diff --git a/modules/images-update-global-pull-secret.adoc b/modules/images-update-global-pull-secret.adoc
index e0b7fd5e42..84569bd682 100644
--- a/modules/images-update-global-pull-secret.adoc
+++ b/modules/images-update-global-pull-secret.adoc
@@ -16,18 +16,10 @@ You can update the global pull secret for your cluster by either replacing the c
 Cluster resources must adjust to the new pull secret, which can temporarily limit the usability of the cluster.
 ====
 
-Updating the global pull secret causes the Machine Config Operator to drain the nodes, apply the change, and uncordon the nodes.
-
-[NOTE]
-====
-As of {product-title} 4.7, changes to the global pull secret no longer trigger a reboot.
-====
-
 .Prerequisites
 
 * You have access to the cluster as a user with the `cluster-admin` role.
 
-
 .Procedure
 . Optional: To append a new pull secret to the existing pull secret, complete the following steps:
 
@@ -60,7 +52,11 @@ Alternatively, you can perform a manual update to the pull secret file.
 $ oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=<pull_secret_location> <1>
 ----
 <1> Provide the path to the new pull secret file.
-
-This update is rolled out to all nodes, which can take some time depending on the size of your cluster. During this time, nodes are drained and pods are rescheduled on the remaining nodes.
-
++
+This update is rolled out to all nodes, which can take some time depending on the size of your cluster. 
++
+[NOTE]
+====
+As of {product-title} 4.7.4, changes to the global pull secret no longer trigger a node drain or reboot.
+====
 //Also referred to as the cluster-wide pull secret.