Changed last step in CLI; Fixed xref in UI section

Author: chrisnegus

modules/olm-deleting-operators-from-a-cluster-using-cli.adoc

@@ -65,14 +65,6 @@ spec:
 ----
 . Remove the Operator from the CatalogSourceConfig in one of two ways:
 
-** If there is only one Operator in the CatalogSourceConfig, you can remove it
-by simply deleting the entire CatalogSourceConfig as follows:
-+
-----
-$ oc delete catalogsourceconfig -n openshift-marketplace \
-    installed-community-openshift-operators
-----
-
 ** If you have multiple Operators, edit the CatalogSourceConfig resource and remove the Operator's package:
 +
 ----
@@ -88,3 +80,11 @@ Remove the package from the `packages` line, as shown:
 ----
 +
 Save the change and the marketplace-operator will reconcile the CatalogSourceConfig.
+
+** If there is only one Operator in the CatalogSourceConfig, you can remove it
+by simply deleting the entire CatalogSourceConfig as follows:
++
+----
+$ oc delete catalogsourceconfig -n openshift-marketplace \
+    installed-community-openshift-operators
+----

modules/olm-deleting-operators-from-a-cluster-using-web-console.adoc

@@ -30,5 +30,5 @@ CRDs, and CRs associated with the Operator.
 Although the Operator is no longer installed or receiving updates, that
 Operator will still appear on the Operator Catalogs list, ready to re-subscribe. To remove the Operator from that
 listing, you can delete the Operator's entry in the CatalogSourceConfig
-from the command line (as shown in the next section).
+from the command line (as shown in last step of "Deleting operators from a cluster using the CLI").
 ====