OSSM-8509: minor edits

rh-tokeefe · rh-tokeefe · commit e6bf212d1e9d · 2025-03-07T17:59:35.000-05:00
diff --git a/modules/ossm-migrating-a-cluster-wide-deployment-using-the-istio-revision-label-with-cert-manager.adoc b/modules/ossm-migrating-a-cluster-wide-deployment-using-the-istio-revision-label-with-cert-manager.adoc
@@ -22,7 +22,7 @@ You can follow these same steps with your own workloads.
 * You created an `IstioCNI` resource.
 * You have the `istioctl` tool installed.
 * You are using the cert-manager and istio-csr tools in a cluster-wide deployment.
-* Your {SMProduct} 2 `ServiceMeshControlPlane` is configured with the cert-manager tool.
+* Your {SMProduct} 2 `ServiceMeshControlPlane` resource is configured with the cert-manager tool.
 
 .Procedure
 
diff --git a/modules/ossm-migrating-workloads-using-the-istio-revision-label-with-cert-manager.adoc b/modules/ossm-migrating-workloads-using-the-istio-revision-label-with-cert-manager.adoc
@@ -6,7 +6,7 @@
 [id="ossm-migrating-workloads-using-the-istio-revision-label-with-cert-manager_{context}"]
 = Migrating workloads using the Istio revision label with cert-manager
 
-Migrate your workloads from the {SMProduct} 2.6 control plane to the {SMproduct} 3.0 control plane.
+Now you can migrate your workloads workloads from the {SMProduct} 2.6 control plane to the {SMproduct} 3.0 control plane.
 
 To maintain simplicity, revision tags are not used in this example. When migrating large meshes, you can use revision tags to avoid re-labeling all namespaces during future 3.y.z upgrades.
 
