Responded to comments on PR 13996

Author: chrisnegus

modules/olm-installing-from-operatorhub-using-cli.adoc

@@ -33,12 +33,13 @@ packageserver            15h
 couchbase-enterprise     14h
 mongodb-enterprise       14h
 etcd                     14h
+myoperator               14h
 ...
 ----
 
 . To identify the Operators to enable on the cluster, create a CatalogSourceConfig
-object YAML file (for example, `csc.cr.yaml`) containing information similar to
-the following:
+object YAML file (for example, `csc.cr.yaml`). Include one or more packages
+listed in the previous step (such as amp-streams or etcd). For example:
 +
 .Example CatalogSourceConfig
 [source,yaml]
@@ -69,7 +70,9 @@ $ oc apply -f csc.cr.yaml
 ----
 
 . Create a Subscription object YAML file (for example, `myoperator-sub.yaml`) to
-subscribe a namespace to an Operator:
+subscribe a namespace to an Operator. Note that the namespace you pick
+must have an OperatorGroup that matches the installMode (either AllNamespaces or
+SingleNamespace modes):
 +
 .Example Subscription
 [source,yaml]

modules/olm-installing-from-operatorhub-using-web-console.adoc

@@ -17,24 +17,27 @@ permissions.
 
 . Navigate in the web console to the *Catalog → Operator Hub* page.
 
-. Choose the Operator you want to install from the list of available Operators (*etcd* for this example), and click *Install*. A pop-up window appears, warning you that you are installing a Community Operator.
+. Choose the Operator you want to install from the list of available Operators (*etcd* for this example).
+A pop-up window appears, warning you that you are installing a Community Operator.
 +
 [NOTE]
 ====
 This Operator will be available under the *Red Hat* category in the GA release.
 ====
-. Select *Continue* to acknowledge the Show Community Operator warning. The Install page appears.
+. Select *Continue* to acknowledge the *Show Community Operator* warning.
 
 . Read the information about the Operator and click *Install*.
 
 . On the *Create Operator Subscription* page, select:
-.. *A specific namespace on the cluster* under Installation Mode to choose a namespace in which the Operator will be available (*default* installs to all namespaces)
+.. Select *All namespaces on the cluster (default)* to install the Operator to all namespaces or
+*A specific namespace on the cluster* to choose a specific, single namespace on which to
+install the Operator. The "All namespaces" option is not always available.
 .. An *Update Channel* (if more than one is available)
-.. *Automatic* or *Manual* Approval Strategy, as described earlier
+.. *Automatic* or *Manual* approval strategy, as described earlier.
 
-. Select the *Subscribe* button to make the Operator available to the selected namespaces on this {product-title} cluster.
+. Click *Subscribe* to make the Operator available to the selected namespaces on this {product-title} cluster.
 
-. Select *Catalog → Installed Operators* page to verify that the *etcd*
+. Select *Catalog → Installed Operators* to verify that the *etcd*
 ClusterServiceVersion (CSV) eventually shows up and its *Status* ultimately
 resolves to *InstallSucceeded*.
 +

modules/olm-operatorhub.adoc

@@ -12,7 +12,7 @@ installed and subscribed on the cluster, and made ready for engineering teams to
 self-service manage the product across deployment environments using the
 Operator Lifecycle Manager (OLM).
 
-Cluster administrators can choose from CatalogSources of Operators grouped into
+Cluster administrators can choose from OperatorSources grouped into
 the following categories:
 
 [cols="2a,8a",options="header"]