MTC: style changes

Author: apinnick

migration/migrating_3_4/deploying-cam-3-4.adoc

@@ -6,21 +6,21 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-You can deploy the {mtc-full} ({mtc-short}) on an {product-title} {product-version} target cluster and an {product-title} 3 source cluster by installing the {mtc-short} Operator. The {mtc-short} Operator deploys {mtc-short} on the target cluster by default.
+You can deploy the {mtc-full} ({mtc-short}) on an {product-title} {product-version} target cluster and an {product-title} 3 source cluster by installing the {mtc-full} Operator. The {mtc-full} Operator deploys {mtc-short} on the target cluster by default.
 
 [NOTE]
 ====
-Optional: You can configure the {mtc-short} Operator to install the {mtc-short} link:https://access.redhat.com/articles/5064151[on an {product-title} 3 cluster or on a remote cluster].
+Optional: You can configure the {mtc-full} Operator to install the {mtc-short} link:https://access.redhat.com/articles/5064151[on an {product-title} 3 cluster or on a remote cluster].
 ====
 
-In a restricted environment, you can install the {mtc-short} Operator from a local mirror registry.
+In a restricted environment, you can install the {mtc-full} Operator from a local mirror registry.
 
-After you have installed the {mtc-short} Operator on your clusters, you can launch the {mtc-short} web console.
+After you have installed the {mtc-full} Operator on your clusters, you can launch the {mtc-short} web console.
 
 [id='installing-cam-operator_{context}']
-== Installing the {mtc-short} Operator
+== Installing the {mtc-full} Operator
 
-You can install the {mtc-short} Operator with the Operator Lifecycle Manager (OLM) on an {product-title} {product-version} target cluster and manually on an {product-title} 3 source cluster.
+You can install the {mtc-full} Operator with the Operator Lifecycle Manager (OLM) on an {product-title} {product-version} target cluster and manually on an {product-title} 3 source cluster.
 
 include::modules/migration-installing-cam-operator-ocp-4.adoc[leveloffset=+2]
 include::modules/migration-installing-cam-operator-ocp-3.adoc[leveloffset=+2]
@@ -29,13 +29,13 @@ include::modules/migration-installing-cam-operator-ocp-3.adoc[leveloffset=+2]
 :context: disconnected-3-4
 :disconnected-3-4:
 [id='installing-cam-operator_{context}']
-== Installing the {mtc-short} Operator in a restricted environment
+== Installing the {mtc-full} Operator in a restricted environment
 
-You can install the {mtc-short} Operator with the Operator Lifecycle Manager (OLM) on an {product-title} {product-version} target cluster and manually on an {product-title} 3 source cluster.
+You can install the {mtc-full} Operator with the Operator Lifecycle Manager (OLM) on an {product-title} {product-version} target cluster and manually on an {product-title} 3 source cluster.
 
-For {product-title} {product-version}, you can build a custom Operator catalog image, push it to a local mirror image registry, and configure OLM to install the {mtc-short} Operator from the local registry. A `mapping.txt` file is created when you run the `oc adm catalog mirror` command.
+For {product-title} {product-version}, you can build a custom Operator catalog image, push it to a local mirror image registry, and configure OLM to install the {mtc-full} Operator from the local registry. A `mapping.txt` file is created when you run the `oc adm catalog mirror` command.
 
-On the {product-title} 3 cluster, you can create a manifest file based on the Operator image and edit the file to point to your local image registry. The `image` value in the manifest file uses the `sha256` value from the `mapping.txt` file. Then, you can use the local image to create the {mtc-short} Operator.
+On the {product-title} 3 cluster, you can create a manifest file based on the Operator image and edit the file to point to your local image registry. The `image` value in the manifest file uses the `sha256` value from the `mapping.txt` file. Then, you can use the local image to create the {mtc-full} Operator.
 
 .Additional resources
 

migration/migrating_3_4/migrating-application-workloads-3-4.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 You can migrate application workloads from {product-title} 3.7, 3.9, 3.10, and 3.11 to {product-title} {product-version} with the {mtc-full} ({mtc-short}). {mtc-short} enables you to control the migration and to minimize application downtime.
 
-The {mtc-short} web console and API, based on Kubernetes Custom Resources, enable you to migrate stateful application workloads at the granularity of a namespace.
+The {mtc-short} web console and API, based on Kubernetes custom resources, enable you to migrate stateful application workloads at the granularity of a namespace.
 
 {mtc-short} supports the file system and snapshot data copy methods for migrating data from the source cluster to the target cluster. You can select a method that is suited for your environment and is supported by your storage provider.
 
@@ -21,7 +21,7 @@ The service catalog is deprecated in {product-title} 4. You can migrate workload
 The {mtc-short} web console displays a message if the service catalog resources cannot be migrated.
 ====
 
-The Control Plane Migration Assistant (CPMA) is a CLI-based tool that assists you in migrating the control plane. The CPMA processes the {product-title} 3 configuration files and generates Custom Resource (CR) manifest files, which are consumed by {product-title} {product-version} Operators.
+The Control Plane Migration Assistant (CPMA) is a CLI-based tool that assists you in migrating the control plane. The CPMA processes the {product-title} 3 configuration files and generates custom resource manifest files, which are consumed by {product-title} {product-version} Operators.
 
 [IMPORTANT]
 ====

migration/migrating_3_4/migrating-with-cpma.adoc

@@ -6,7 +6,7 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-The Control Plane Migration Assistant (CPMA) is a CLI-based tool that assists you in migrating the control plane from {product-title} 3.7 (or later) to {product-version}. The CPMA processes the {product-title} 3 configuration files and generates Custom Resource (CR) manifest files, which are consumed by {product-title} {product-version} Operators.
+The Control Plane Migration Assistant (CPMA) is a CLI-based tool that assists you in migrating the control plane from {product-title} 3.7 (or later) to {product-version}. The CPMA processes the {product-title} 3 configuration files and generates custom resource manifest files, which are consumed by {product-title} {product-version} Operators.
 
 include::modules/migration-installing-cpma.adoc[leveloffset=+1]
 include::modules/migration-using-cpma.adoc[leveloffset=+1]