diff --git a/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc b/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc
index 0bcea2a467..389ed6d2a2 100644
--- a/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc
+++ b/mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc
@@ -67,7 +67,7 @@ data:
   .dockerconfigjson: <encoded_docker_configuration> <2>
 type: kubernetes.io/dockerconfigjson
 ----
-<1> The `namespace` value must match the target namespace.
+<1> Ensure that the `namespace` value matches the target namespace.
 <2> Specify the base64-encoded configuration file as the value. 
 
 . Apply the file to create the resource. Run the following command on the hub cluster:
@@ -98,7 +98,7 @@ metadata:
   namespace: "example-sno" <1>
 type: Opaque
 ----
-<1> The `namespace` value must match the target namespace.
+<1> Ensure that the `namespace` value matches the target namespace.
 
 . Apply the file to create the resource. Run the following command on the hub cluster:
 
@@ -148,7 +148,7 @@ data:
       containerRuntimeConfig:
         defaultRuntime: crun
 ----
-<1> The `namespace` value must match the target namespace.
+<1> Ensure that the `namespace` value matches the target namespace.
 
 . Create the resource by running the following command on the hub cluster:
 
@@ -198,13 +198,13 @@ spec:
           namespace: rhacm
       [...]
 ----
-<1> The `namespace` in the `ClusterInstance` custom resource must match the target namespace that you defined.
+<1> Ensure that the `namespace` in the `ClusterInstance` custom resource matches the target namespace that you defined.
 <2> Reference the `name` of one or more extra manifests `ConfigMap` objects.
 <3> Reference the `name` of your pull secret.
-<4> The value of the `clusterName` field in the `ClusterInstance` custom resource must match the value of the `namespace` field.
-<5> Reference the `name` of the cluster-level templates under the `spec.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
+<4> Ensure that the value of the `clusterName` field in the `ClusterInstance` custom resource matches the value of the `namespace` field.
+<5> Reference the `name` of the cluster-level templates in the `spec.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
 <6> Reference the `name` of the BMC secret.
-<7> Reference the `name` of the node-level templates under the `spec.nodes.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
+<7> Reference the `name` of the node-level templates in the `spec.nodes.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
 
 . Apply the file and create the resource by running the following command: