diff --git a/modules/deleting-wmco-namespace.adoc b/modules/deleting-wmco-namespace.adoc
index 2745967f4643..f2bafa8d0b0e 100644
--- a/modules/deleting-wmco-namespace.adoc
+++ b/modules/deleting-wmco-namespace.adoc
@@ -4,31 +4,57 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="deleting-wmco-namespace_{context}"]
-= Deleting the Windows Machine Config Operator namespace
+= Deleting the Windows Machine Config Operator namespace and operands
 
-You can delete the namespace that was generated for the Windows Machine Config Operator (WMCO) by default.
+After removing the Windows Machine Config Operator, it is recommended that you remove the other components associated with the Operator to avoid potential issues.
 
 .Prerequisites
 
+* The Windows `Machine` objects that hosted your Windows workloads are removed from your cluster.
 * The WMCO is removed from your cluster.
 
 .Procedure
 
-. Remove all Windows workloads that were created in the `openshift-windows-machine-config-operator` namespace:
+This procedure assumes that you are using the default `openshift-windows-machine-config-operator` namespace.
+
+. Remove all WMCO resources that were created in the `openshift-windows-machine-config-operator` namespace by using the following command:
 +
 [source,terminal]
 ----
 $ oc delete --all pods --namespace=openshift-windows-machine-config-operator
 ----
++
+[NOTE]
+====
+The `openshift-windows-machine-config-operator` namespace is reserved for WMCO resources. There should be no Windows workloads or pods in the namespace.
+====
 
-. Verify that all pods in the `openshift-windows-machine-config-operator` namespace are deleted or are reporting a terminating state:
+. Verify that all pods in the `openshift-windows-machine-config-operator` namespace are deleted or are reporting a terminating state by using the following command:
 +
 [source,terminal]
 ----
 $ oc get pods --namespace openshift-windows-machine-config-operator
 ----
++
+.Example output
+[source,terminal]
+----
+No resources found in openshift-windows-machine-config-operator namespace.
+----
+
+. Delete RBAC resources by using the following command:
++
+[source,terminal]
+----
+$ oc delete clusterrolebinding windows-instance-config-daemon
+----
++
+[source,terminal]
+----
+$ oc delete clusterroles windows-instance-config-daemon
+----
 
-. Delete the `openshift-windows-machine-config-operator` namespace:
+. Delete the `openshift-windows-machine-config-operator` namespace by using the following command:
 +
 [source,terminal]
 ----
diff --git a/modules/uninstalling-wmco.adoc b/modules/uninstalling-wmco.adoc
index 3a0ca2c9c2dc..1144c19a0223 100644
--- a/modules/uninstalling-wmco.adoc
+++ b/modules/uninstalling-wmco.adoc
@@ -14,7 +14,7 @@ You can uninstall the Windows Machine Config Operator (WMCO) from your cluster.
 
 .Procedure
 
-. From the *Operators -> OperatorHub* page, use the *Filter by keyword* box to search for `Red Hat Windows Machine Config Operator`.
+. From the *Operators -> OperatorHub* page, use the *Filter by keyword* box to search for `Windows Machine Config Operator`.
 
 . Click the *Red Hat Windows Machine Config Operator* tile. The Operator tile indicates it is installed.