diff --git a/modules/ossm-about-adding-namespace.adoc b/modules/ossm-about-adding-namespace.adoc
index 6b46b8478a..33aaf3ab30 100644
--- a/modules/ossm-about-adding-namespace.adoc
+++ b/modules/ossm-about-adding-namespace.adoc
@@ -17,7 +17,7 @@ You can add projects to an existing service mesh using either the {product-title
 
 * Specifying the project name in the `ServiceMeshMemberRoll` resource.
 
-* Configuring label selectors in the `spec.labelSelectors` field of the `ServiceMeshMemberRoll` resource.
+* Configuring label selectors in the `spec.memberSelectors` field of the `ServiceMeshMemberRoll` resource.
 
 * Creating the `ServiceMeshMember` resource in the project.
 
diff --git a/modules/ossm-deploy-cluster-wide-mesh.adoc b/modules/ossm-deploy-cluster-wide-mesh.adoc
index 919f396785..fc2dd5f222 100644
--- a/modules/ossm-deploy-cluster-wide-mesh.adoc
+++ b/modules/ossm-deploy-cluster-wide-mesh.adoc
@@ -7,4 +7,4 @@
 
 A cluster-wide deployment contains a Service Mesh Control Plane that monitors resources for an entire cluster. Monitoring resources for an entire cluster closely resembles Istio functionality in that the control plane uses a single query across all namespaces to monitor Istio and Kubernetes resources. As a result, cluster-wide deployments decrease the number of requests sent to the API server.
 
-Similar to Istio, a cluster-wide mesh includes namespaces with the `istio-injection=enabled` namespace label by default. You can change this label by modifying the `spec.labelSelectors` field of the `ServiceMeshMemberRoll` resource.
+Similar to Istio, a cluster-wide mesh includes namespaces with the `istio-injection=enabled` namespace label by default. You can change this label by modifying the `spec.memberSelectors` field of the `ServiceMeshMemberRoll` resource.