OSSMDOC-373: Update control plane references

Author: rh-tokeefe

modules/jaeger-removing-instance-cli.adoc

@@ -4,7 +4,7 @@ This module included in the following assemblies:
 ////
 :pantheon-module-type: PROCEDURE
 [id="jaeger-removing-cli_{context}"]
-= Removing a Jaeger instance from the CLI
+= Removing a Jaeger instance using the CLI
 
 
 . Log in to the {product-title} CLI.

modules/ossm-about-collecting-ossm-data.adoc

@@ -25,7 +25,7 @@ You can use the `oc adm must-gather` CLI command to collect information about yo
 $ oc adm must-gather --image=registry.redhat.io/openshift-service-mesh/istio-must-gather-rhel8
 ----
 +
-. To collect {SMProductName} data for a specific control plane namespace with `must-gather`, you must specify the {SMProductName} image and namespace. In this example, replace  `<namespace>` with your control plane namespace, such as `istio-system`.
+. To collect {SMProductName} data for a specific {SMProductShortName} control plane namespace with `must-gather`, you must specify the {SMProductName} image and namespace. In this example, replace  `<namespace>` with your {SMProductShortName} control plane namespace, such as `istio-system`.
 +
 [source,terminal]
 ----

modules/ossm-access-grafana.adoc

@@ -6,13 +6,13 @@
 [id="ossm-access-grafana_{context}"]
 = Accessing the Grafana console
 
-Grafana is an analytics tool that you can use to view, query, and analyze your service mesh metrics. In this example, `istio-system` is the control plane namespace. To access Grafana, do the following:
+Grafana is an analytics tool you can use to view, query, and analyze your service mesh metrics. In this example, `istio-system` is the {SMProductShortName} control plane namespace. To access Grafana, do the following:
 
 .Procedure
 
 . Log in to the {product-title} web console.
 
-. Click the *Project* menu and select the project where you installed the control plane, for example *istio-system*.
+. Click the *Project* menu and select the project where you installed the {SMProductShortName} control plane, for example *istio-system*.
 
 . Click *Routes*.
 

modules/ossm-access-prometheus.adoc

@@ -6,13 +6,13 @@
 [id="ossm-access-prometheus_{context}"]
 = Accessing the Prometheus console
 
-Prometheus is a monitoring and alerting tool that you can use to collect multi-dimensional data about your microservices. In this example, `istio-system` is the control plane namespace.
+Prometheus is a monitoring and alerting tool that you can use to collect multi-dimensional data about your microservices. In this example, `istio-system` is the {SMProductShortName} control plane namespace.
 
 .Procedure
 
 . Log in to the {product-title} web console.
 
-. Click the *Project* menu and select the project where you installed the control plane, for example *istio-system*.
+. Click the *Project* menu and select the project where you installed the {SMProductShortName} control plane, for example *istio-system*.
 
 . Click *Routes*.
 

modules/ossm-accessing-jaeger.adoc

@@ -1,6 +1,7 @@
 // Module included in the following assemblies:
 // * service_mesh/v2x/-ossm-troubleshooting-istio.adoc
 
+:_content-type: PROCEDURE
 [id="ossm-accessing-jaeger_{context}"]
 = Accessing the Jaeger console
 ////
@@ -18,7 +19,7 @@ The deployment process creates a route to access the Jaeger console.
 . Navigate to *Networking* -> *Routes* and
 search for the Jaeger route, which is the URL listed under *Location*.
 
-. To query for details of the route using the command line, enter the following command. In this example, `istio-system` is the control plane namespace.
+. To query for details of the route using the command line, enter the following command. In this example, `istio-system` is the {SMProductShortName} control plane namespace.
 +
 [source,terminal]
 ----

modules/ossm-accessing-kiali.adoc

@@ -1,6 +1,7 @@
 // Module included in the following assemblies:
 // * service_mesh/v2x/-ossm-troubleshooting-istio.adoc
 
+:_content-type: PROCEDURE
 [id="ossm-accessing-kiali_{context}"]
 = Accessing the Kiali console
 

modules/ossm-auto-route.adoc

@@ -2,6 +2,7 @@
 // * service_mesh/v2x/ossm-traffic-manage.adoc
 //
 
+:_content-type: PROCEDURE
 [id="ossm-auto-route-create-subdomains_{context}"]
 = Creating subdomain routes
 
@@ -26,7 +27,7 @@ spec:
     - bookinfo.example.com
 ----
 
-Then, the following OpenShift Routes are created automatically. You can check that the routes are created with the following command. In this example, `istio-system` is the name of the control plane project.
+The 'Gateway' resource creates the following OpenShift Routes. You can check that the routes are created by using the following command. In this example, `istio-system` is the name of the {SMProductShortName} control plane project.
 
 [source,terminal]
 ----

modules/ossm-config-disable-networkpolicy.adoc

@@ -22,7 +22,7 @@ When you disable `spec.security.manageNetworkPolicy` {SMProductName} will not cr
 
 . In the {product-title} web console, click *Operators* -> *Installed Operators*.
 
-. Select the project where you installed the control plane, for example `istio-system`, from the *Project* menu.
+. Select the project where you installed the {SMProductShortName} control plane, for example `istio-system`, from the *Project* menu.
 
 . Click the {SMProductName} Operator. In the *Istio Service Mesh Control Plane* column, click the name of your `ServiceMeshControlPlane`, for example `basic-install`.
 

modules/ossm-config-enabling-controlplane.adoc

@@ -2,10 +2,11 @@
 //
 // * service_mesh/v2x/ossm-config.adoc
 
+:_content-type: PROCEDURE
 [id="ossm-security-enabling-controlplane_{context}"]
 == Enabling strict mTLS for Mixer telemetry or policy components
 
-Secure connections are always used when proxies communicate with the control plane regardless of the `spec.security.controlPlane.mtls` setting. If Mixer telemetry or policies are part of your configuration, set `spec.security.controlPlane.mtls` to `true` in your `ServiceMeshControlPlane` resource to enable strict mTLS.
+Secure connections are always used when proxies communicate with the {SMProductShortName} control plane regardless of the `spec.security.controlPlane.mtls` setting. If Mixer telemetry or policies are part of your configuration, set `spec.security.controlPlane.mtls` to `true` in your `ServiceMeshControlPlane` resource to enable strict mTLS.
 
 [source,yaml, subs="attributes,verbatim"]
 ----
@@ -18,13 +19,13 @@ spec:
       mtls: true
 ----
 
-You can also enable mTLS for the control plane by using the {product-title} web console. In this example, `istio-system` is the control plane namespace.
+You can also enable mTLS for the {SMProductShortName} control plane by using the {product-title} web console. In this example, `istio-system` is the {SMProductShortName} control plane namespace.
 
 .Procedure
 
 . Log in to the web console.
 
-. Click the *Project* menu and select the project where you installed the control plane, for example *istio-system*.
+. Click the *Project* menu and select the project where you installed the {SMProductShortName} control plane, for example *istio-system*.
 
 . Click *Operators* -> *Installed Operators*.
 

modules/ossm-config-external-jaeger.adoc

@@ -17,7 +17,7 @@ If you already have an existing {JaegerName} instance in {product-title}, you ca
 
 . In the {product-title} web console, click *Operators* -> *Installed Operators*.
 
-. Click the *Project* menu and select the project where you installed the control plane, for example *istio-system*.
+. Click the *Project* menu and select the project where you installed the {SMProductShortName} control plane, for example *istio-system*.
 
 . Click the {SMProductName} Operator. In the *Istio Service Mesh Control Plane* column, click the name of your `ServiceMeshControlPlane` resource, for example `basic`.