Implemented OCP peer review comments

Author: amolnar-rh

modules/ztp-removing-content-from-managed-clusters.adoc

@@ -6,14 +6,13 @@
 [id="ztp-removing-content-from-managed-clusters_{context}"]
 = Changing applied managed cluster CRs using policies
 
-You can remove content from a custom resource (CR) deployed to a managed cluster through a policy.
+You can remove content from a custom resource (CR) that is deployed in a managed cluster through a policy.
 
-By default, all `Policy` CRs created from a `PolicyGenTemplate` CR have a `complianceType` set to `musthave`.
-In this mode, when you remove a field from a CR, the value is removed from the policy but is not removed from the CR on the managed cluster.
-A `musthave` policy without the removed field is still compliant because the CR on the managed cluster has all the specified content.
+By default, all `Policy` CRs created from a `PolicyGenTemplate` CR have the `complianceType` field set to `musthave`.
+A `musthave` policy without the removed content is still compliant because the CR on the managed cluster has all the specified content.
+In this configuration, when you remove content from a CR, {cgu-operator} removes it from the policy but the content is not removed from the CR on the managed cluster.
 
-To remove the content from the managed cluster, set the `complianceType` field to `mustonlyhave`.
-In this mode, the policy ensures that the CR on the cluster is an exact match of what is specified in the policy.
+With the `complianceType` field to `mustonlyhave`, the policy ensures that the CR on the cluster is an exact match of what is specified in the policy.
 
 .Prerequisites
 
@@ -27,7 +26,7 @@ In this mode, the policy ensures that the CR on the cluster is an exact match of
 
 .Procedure
 
-. Remove the content that you no longer need from the affected CRs. In this example, the `disableDrain: false` line should be removed from the `SriovOperatorConfig` CR.
+. Remove the content that you no longer need from the affected CRs. In this example, the `disableDrain: false` line was removed from the `SriovOperatorConfig` CR.
 +
 .Example CR
 
@@ -38,28 +37,27 @@ kind: SriovOperatorConfig
 metadata:
   name: default
   namespace: openshift-sriov-network-operator
-  annotations:
-    ran.openshift.io/ztp-deploy-wave: "10"
 spec:
   configDaemonNodeSelector:
     "node-role.kubernetes.io/$mcp": ""
-  disableDrain: true <1>
+  disableDrain: true
   enableInjector: true
   enableOperatorWebhook: true
 ----
-<1> Remove the `disableDrain: true` line.
 
 . Change the `complianceType` of the affected policies to `mustonlyhave` in the `group-du-sno-ranGen.yaml` file.
 +
 .Example YAML
 [source,yaml]
 ----
+# ...
 - fileName: SriovOperatorConfig.yaml
   policyName: "config-policy"
   complianceType: mustonlyhave
+# ...
 ----
 
-. Create a `ClusterGroupUpdates` CR and specify the clusters you want to deploy the changes to:
+. Create a `ClusterGroupUpdates` CR and specify the clusters that must receive the CR changes::
 +
 .Example ClusterGroupUpdates CR
 [source,yaml]
@@ -97,11 +95,13 @@ $ oc --namespace=default patch clustergroupupgrade.ran.openshift.io/cgu-remove \
 --patch '{"spec":{"enable":true}}' --type=merge
 ----
 
+.Verification
+
 . Check the status of the policies by running the following command:
 +
 [source,terminal]
 ----
-$ oc get <changed_cr>
+$ oc get <kind> <changed_cr_name>
 ----
 
 +
@@ -116,13 +116,11 @@ default     ztp-group.group-du-sno-config-policy                   inform
 +
 When the `COMPLIANCE STATE` of the policy is `Compliant`, it means that the CR is updated and the unwanted content is removed.
 
-.Verification
-
 * Check that the policies are removed from the targeted clusters by running the following command on the managed clusters:
 +
 [source,terminal]
 ----
-$ oc get <changed_cr>
+$ oc get <kind> <changed_cr_name>
 ----
 
 +