Update v_2.1.0.md

docs/v_2.1.0.md

@@ -22,9 +22,9 @@
 [v2.1.0]: https://github.com/kubernetes-sigs/kustomize/releases/tag/v2.1.0
 [versioning policy]: versioningPolicy.md
 
-_Summary_: Go modules, resource ordering respected, generator and transformer plugins, eased
-loading restrictions, some kustomization field changes and about ~90 issues closed
-since [v2.0.3] (over 400 commits).
+Go modules, resource ordering respected, generator and transformer plugins, eased
+loading restrictions, the notion of inventory, eased replica count modification.
+About ~90 issues closed since [v2.0.3] in ~400 commits.
 
 ## Go modules
 
@@ -42,7 +42,17 @@ kustomize plugins (see below).
 ![sort order retained][imgSorted]
 
 Kustomize now retains the depth-first order of
-resources as read.
+resources as read, a frequently requested
+feature.
+
+This means resource order can be controlled
+by editting kustomization files.  This is
+also vital to applying user-defined
+transformations (plugins) in a particular
+order.
+
+Nothing needs to be done to activate this;
+it happens automatically.
 
 The `build` command now accepts a `--reorder`
 flag with values `legacy` and `none`,
@@ -51,13 +61,13 @@ with a default value of `legacy`.
 `legacy` means apply an ordering based on
 GVK, that currently emits `Namespace` objects
 first, and `ValidatingWebhookConfiguration`
-objects last.
+objects last.  This means that despite
+automatic retention of load order, your
+`build` output won't change by default.
 
-`none` means do not reorder the resources before
-output.  This means kustomize respects the input
-order of the data, giving the user a means to
-control output order.  Generated resources always
-come last.
+`none` means _don't_ reorder the resources before
+output.  Specify this to see output order
+respect input order.
 
 ## Generator and transformer plugins