editing pass

samples/README.md

@@ -5,18 +5,20 @@ different Pod-creating Kubernetes resources in an AppWrapper.
 AppWrappers can be used to wrap any Kubernetes Kind that uses `PodSpecTemplate`
 to express its Pods.
 
-An AppWrapper contains a `component` array of `AppWrapperComponents`.
+An AppWrapper contains a`components` array containing the wrapped resources.
 Each component has two main pieces: a `template` that defines the wrapped resource
 and a `podSets` array that gives the `replicas` and `path` within the template
 for each `PodSpecTemplate`.   For correct operation of the AppWrapper, it is
 required that the provided `path` and `replicas` information correctly represent
-the Pod creating behavior of the wrapped resource.
+the Pod creating behavior of the wrapped resource.  For resources that do not
+created Pods (eg `Services` or `Secrets`) `podSets` should be empty and thus omitted.
 
 To simplify the user experience, for a selection of commonly-used Kubernetes
 resource Kinds, the AppWrapper controller can automatically infer the `podSets`
-array if it is not provided. For these same kinds, the AppWrapper controller
-will validate that any explicitly provided `podSet` entries match the definitions in
-`template`. The current set of automatically inferred Kinds is:
+array if it is not provided. For these same Kinds, the AppWrapper controller
+will validate that any explicitly provided `podSet` entries do in fact match the
+definitions in `template`.
+The current set of automatically inferred Kinds is:
    + v1 Pod
    + apps/v1 Deployment
    + apps/v1 StatefulSet
@@ -25,5 +27,5 @@ will validate that any explicitly provided `podSet` entries match the definition
    + ray.io/v1 RayCluster
    + ray.io/v1 RayJob
 
-In all the examples, if the Kind supports automatic inference the `podSets`
-are elided.
+In all of the examples, if automatic inference is supported for the wrapped Kind,
+the `podSets` are omitted from the AppWrapper.