Tweak docs readme

docs/README.md

@@ -1,12 +1,13 @@
 # Kustomize docs
    
- * [glossary](glossary.md) - glossary for Kustomize.
+ * [kustomization.yaml](kustomization.yaml) - Example of a
- 
+   [kustomization](glossary.md#kustomization)
- * [Sample kustomization.yaml](kustomization.yaml) - A sample kustomization.yaml
+   with explanations of each field.
-   with explanation for each field.
+
-   
+ * [workflow](workflows.md) - Some steps one might take in using
- * [workflow](workflows.md) - Explaining the workflow for
+   bespoke and off-the-shelf configurations.
-   both bespoke configuration and off-the-shelf configuration.
   
- * [eschewed features](eschewedFeatures.md) - explaining the eschewed features
+ * [glossary](glossary.md) - An attempt to disambiguiate terminology.
-    and why they are not supported in Kustomize.
+   
+ * [eschewed features](eschewedFeatures.md) - Why certain features are (currently)
+   not supported in Kustomize.

docs/workflows.md

@@ -21,14 +21,17 @@ use and maintain a configuration.
 
 ## Bespoke configuration
 
-In this workflow, all configuration files are owned by
+In this workflow, all configuration (resource YAML) files
-the user.  No content is incorporated from version
+are owned by the user.  No content is incorporated from version
 control repositories owned by others.
 
 ![bespoke config workflow image][workflowBespoke]
 
 #### 1) create a directory in version control
 
+Speculate some overall cluster application called _ldap_;
+we want to keep its configuration in its own repo.
+
 > ```
 > git init ~/ldap
 > ```