Merge pull request #80255 from gwynnemonahan/OSSM-6920

OSSM-6920 [DOC] OTEL + Tempo Merge Review Clean up

Author: adellape

modules/ossm-configuring-distr-tracing-tempo.adoc

@@ -15,9 +15,9 @@ You can create a {OTELName} instance in a mesh namespace and configure it to sen
 
 .Prerequisites
 
-* You created a TempoStack instance using the Red Hat {TempoOperator} in the `tracing-system` namespace. For more information, see "Installing {TempoName}" in the "Additional resources" section.
+* You created a TempoStack instance using the Red Hat {TempoOperator} in the `tracing-system` namespace. For more information, see "Installing {TempoName}".
 
-* You installed the {OTELOperator} in either the recommended namespace or the `openshift-operators` namespace. For more information, see "Installing the {OTELName}" in the "Additional resources" section.
+* You installed the {OTELOperator} in either the recommended namespace or the `openshift-operators` namespace. For more information, see "Installing the {OTELName}".
 
 * If using {SMProductName} 2.5 or earlier, set the `spec.tracing.type` parameter of the `ServiceMeshControlPlane` resource to `None` so tracing data can be sent to the OpenTelemetry Collector.
 
@@ -64,7 +64,7 @@ spec:
 You only need to create one instance of the OpenTelemetry Collector in one of the `ServiceMeshMemberRoll` member namespaces.
 ====
 
-. Check the `otel-collector` pod log and verify that the pod is running.
+. Check the `otel-collector` pod log and verify that the pod is running:
 +
 .Example `otel-collector` pod log check
 [source,terminal]