OCPBUGS-60988: Added update secret step to insights-operator-new-pull-secret

Author: dfitzmau

modules/insights-operator-new-pull-secret-disabled.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="insights-operator-new-pull-secret_{context}"]
-= Modifying the global cluster pull secret to disable remote health reporting
+= Changing the global cluster pull secret to disable remote health reporting
 
-You can modify your existing global cluster pull secret to disable remote health reporting. This disables both Telemetry and the Insights Operator.
+You can change your existing global cluster pull secret to disable remote health reporting. This configuration disables both Telemetry and the Insights Operator.
 
 .Prerequisites
 
@@ -19,16 +19,14 @@ endif::openshift-rosa,openshift-dedicated[]
 
 .Procedure
 
-. Download the global cluster pull secret to your local file system.
+. Download the global cluster pull secret to your local file system:
 +
 [source,terminal]
 ----
 $ oc extract secret/pull-secret -n openshift-config --to=.
 ----
 
-. In a text editor, edit the `.dockerconfigjson` file that was downloaded.
-
-. Remove the `cloud.openshift.com` JSON entry, for example:
+. In a text editor, edit the `.dockerconfigjson` file that you downloaded by removing the `cloud.openshift.com` JSON entry:
 +
 [source,json]
 ----
@@ -37,4 +35,13 @@ $ oc extract secret/pull-secret -n openshift-config --to=.
 
 . Save the file.
 
-You can now update your cluster to use this modified pull secret.
+. Update the secret in your cluster by running the following command:
++
+[source,terminal]
+----
+$ oc set data secret/pull-secret -n openshift-config \
+  --from-file=.dockerconfigjson=pull-secret
+----
++
+You might need to wait several minutes for the secret to update in your cluster. 
+

modules/insights-operator-new-pull-secret-enable.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="insights-operator-new-pull-secret-enable_{context}"]
-= Modifying your global cluster pull secret to enable remote health reporting
+= Changing your global cluster pull secret to enable remote health reporting
 
-You can modify your existing global cluster pull secret to enable remote health reporting. If you have previously disabled remote health monitoring, you must first download a new pull secret with your `console.openshift.com` access token from {cluster-manager-first}.
+You can change your existing global cluster pull secret to enable remote health reporting. If you have disabled remote health monitoring, you must first download a new pull secret with your `console.openshift.com` access token from {cluster-manager-first}.
 
 .Prerequisites
 
@@ -16,6 +16,7 @@ You can modify your existing global cluster pull secret to enable remote health
 .Procedure
 
 . Navigate to link:https://console.redhat.com/openshift/downloads[https://console.redhat.com/openshift/downloads].
+
 . From *Tokens* -> *Pull Secret*, click *Download*.
 +
 The file `pull-secret.txt` containing your `cloud.openshift.com` access token in JSON format downloads:
@@ -40,26 +41,32 @@ $ oc get secret/pull-secret -n openshift-config \
   --template='{{index .data ".dockerconfigjson" | base64decode}}' \
   > pull-secret
 ----
+
 . Make a backup copy of your pull secret.
 +
 [source,terminal]
 ----
 $ cp pull-secret pull-secret-backup
 ----
+
 . Open the `pull-secret` file in a text editor.
+
 . Append the `cloud.openshift.com` JSON entry from `pull-secret.txt` into `auths`.
+
 . Save the file.
-. Update the secret in your cluster.
+
+. Update the secret in your cluster by running the following command:
 +
 [source,terminal]
 ----
 $ oc set data secret/pull-secret -n openshift-config \
   --from-file=.dockerconfigjson=pull-secret
 ----
-
-It may take several minutes for the secret to update and your cluster to begin reporting.
++
+You might need to wait several minutes for the secret to update and your cluster to begin reporting.
 
 .Verification
 
 . Navigate to the {product-title} Web Console Overview page.
+
 . *Insights* in the *Status* tile reports the number of issues found.

support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc

@@ -24,8 +24,13 @@ To opt out of remote health reporting, you must:
 
 include::modules/telemetry-consequences-of-disabling-telemetry.adoc[leveloffset=+1]
 
+// Changing the global cluster pull secret to disable remote health reporting
 include::modules/insights-operator-new-pull-secret-disabled.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../support/remote-health-monitoring-with-connected-clusters#images-update-global-pull-secret_opting-out-remote-health-reporting[Changing your global cluster pull secret to enable remote health reporting]
+
 include::modules/insights-operator-register-disconnected-cluster.adoc[leveloffset=+1]
 
 [role="_additional-resources"]