Merge pull request #32953 from neal-timpe/ossmdoc-302

OSSMDOC-302: Upgrading review

Author: mikemckiernan

service_mesh/v2x/upgrading-ossm.adoc

@@ -5,7 +5,7 @@ include::modules/ossm-document-attributes.adoc[]
 
 toc::[]
 
-To access the most current features of {ProductName}, upgrade to the current version, 2.0. Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and apps to a new instance of {ProductName} running the new version.
+Upgrading from version 1.1 to 2.0 requires manual steps that migrate your workloads and application to a new instance of {ProductName} running the new version.
 
 .Prerequisites
 
@@ -368,7 +368,7 @@ Istiod manages client certificates and private keys used by service proxies. By
 [id="ossm-upgrading-config-tracing_{context}"]
 === Tracing
 
-_Tracing_ is configured under `spec.tracing`. Currently, the only type of tracer that is supported is `Jaeger`. Sampling is a scaled integer representing 0.01% increments, for example, 1 is 0.01% and 10000 is 100%. The tracing implementation and sampling rate can be specified:
+Tracing is configured in `spec.tracing`. Currently, the only type of tracer that is supported is `Jaeger`. Sampling is a scaled integer representing 0.01% increments, for example, 1 is 0.01% and 10000 is 100%. The tracing implementation and sampling rate can be specified:
 
 [source,yaml]
 ----
@@ -378,7 +378,7 @@ spec:
     type: Jaeger
 ----
 
-_Jaeger_ is configured under the addons section of the SMCP spec.
+Jaeger is configured in the addons section of the `ServiceMeshControlPlane` resource.
 
 [source,yaml]
 ----
@@ -430,7 +430,7 @@ spec:
       install: {} # customize install
 ----
 
-The Grafana and Kiali installations can be somewhat customized through their respective `install` fields. Container customization, such as resource limits, is configured in `spec.runtime.components.kiali` and `spec.runtime.components.grafana`. If an existing Kiali resource matching the value of name exists, the control plane configures the Kiali resource for use with the control plane. Some fields in the Kiali resource are overridden, such as the `accessible_namespaces` list, as well as the endpoints for Grafana, Prometheus, and tracing. Use an existing resource to fully customize your Kiali installation.
+The Grafana and Kiali installations can be customized through their respective `install` fields. Container customization, such as resource limits, is configured in `spec.runtime.components.kiali` and `spec.runtime.components.grafana`. If an existing Kiali resource matching the value of name exists, the control plane configures the Kiali resource for use with the control plane. Some fields in the Kiali resource are overridden, such as the `accessible_namespaces` list, as well as the endpoints for Grafana, Prometheus, and tracing. Use an existing resource to fully customize your Kiali installation.
 
 === Resource utilization and scheduling