openshift · max-cx · Jun 19, 2026
diff --git a/config-instrumentation/otel-configuration-of-instrumentation.adoc b/config-instrumentation/otel-configuration-of-instrumentation.adoc
@@ -1,13 +1,13 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="otel-configuration-of-instrumentation"]
-= Configuring the instrumentation
+= Instrument your application
 :context: otel-configuration-of-instrumentation
 
 toc::[]
 
 [role="_abstract"]
-The {OTelOperator} uses an `Instrumentation` custom resource that defines the configuration of the instrumentation.
+Use the `Instrumentation` custom resource of the {OTelOperator} to configure the instrumentation.
 
 include::modules/otel-autoinstrumentation.adoc[leveloffset=+1]
 

diff --git a/installing/otel-installing.adoc b/installing/otel-installing.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="install-otel"]
-= Installing
+= Install the {otel}
 :context: install-otel
 
 toc::[]

diff --git a/migrating/otel-migrating.adoc b/migrating/otel-migrating.adoc
@@ -1,11 +1,14 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="otel-migrating"]
-= Migrating
+= Migrate from Jaeger
 :context: otel-migrating
 
 toc::[]
 
+[role="_abstract"]
+If you are already using the {JaegerName} for your applications, you can migrate to the {otel}, which is based on the link:https://opentelemetry.io/[OpenTelemetry] open source project.
+
 include::snippets/distr-tracing-assembly-tip-for-jaeger-replacements.adoc[]
 
 include::modules/otel-migrating-overview.adoc[leveloffset=+1]

diff --git a/modules/otel-autoinstrumentation.adoc b/modules/otel-autoinstrumentation.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="otel-autoinstrumentation_{context}"]
-= Auto-instrumentation in the {OTelOperator}
+= About auto-instrumentation
 
 [role="_abstract"]
 Auto-instrumentation in the {OTelOperator} can automatically instrument an application without manual code changes. Developers and administrators can monitor applications with minimal effort and changes to the existing codebase.

diff --git a/modules/otel-collector-deployment-modes.adoc b/modules/otel-collector-deployment-modes.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: REFERENCE
 [id="otel-collector-deployment-modes_{context}"]
-= OpenTelemetry Collector deployment modes
+= Collector deployment modes
 
 [role="_abstract"]
 The `OpenTelemetryCollector` custom resource allows you to specify one of the following deployment modes for the OpenTelemetry Collector:

diff --git a/modules/otel-config-instrumentation.adoc b/modules/otel-config-instrumentation.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: REFERENCE
 [id="otel-instrumentation-config_{context}"]
-= OpenTelemetry instrumentation configuration options
+= Instrumentation configuration
 
 [role="_abstract"]
 The {otel} injects and configures the OpenTelemetry auto-instrumentation libraries into your workloads. Currently, the {otel} supports injecting instrumentation libraries for Go, Java, Node.js, Python, .NET, and the Apache HTTP Server (`httpd`).

diff --git a/modules/otel-creating-required-RBAC-resources-automatically.adoc b/modules/otel-creating-required-RBAC-resources-automatically.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="otel-creating-required-RBAC-resources-automatically_{context}"]
-= Creating the required RBAC resources automatically
+= Create the required RBAC resources automatically
 
 [role="_abstract"]
 Some Collector components require configuring the RBAC resources.

diff --git a/modules/otel-install-cli.adoc b/modules/otel-install-cli.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="installing-otel-by-using-the-cli_{context}"]
-= Installing the {otel} by using the CLI
+= Install the {otel} from the command line
 
 [role="_abstract"]
 You can install the {otel} from the command line.

diff --git a/modules/otel-install-taints-and-tolerations.adoc b/modules/otel-install-taints-and-tolerations.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="otel-install-taints-and-tolerations_{context}"]
-= Using taints and tolerations
+= Taints and tolerations
 
 [role="_abstract"]
 To schedule the OpenTelemetry pods on dedicated nodes, see link:https://access.redhat.com/solutions/7040771[How to deploy the different OpenTelemetry components on infra nodes by using a node selector and tolerations in OpenShift 4]
diff --git a/modules/otel-install-web-console.adoc b/modules/otel-install-web-console.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="installing-otel-by-using-the-web-console_{context}"]
-= Installing the {otel} from the web console
+= Install the {otel} from the web console
 
 [role="_abstract"]
 You can install the {otel} from the {ocp-product-title} web console.

diff --git a/modules/otel-migrating-from-jaeger-with-sidecars.adoc b/modules/otel-migrating-from-jaeger-with-sidecars.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="migrating-to-otel-from-jaeger-with-sidecars_{context}"]
-= Migrating with sidecars
+= Migrate with sidecars
 
 [role="_abstract"]
 The {OTelOperator} supports sidecar injection into deployment workloads, so you can migrate from a {JaegerShortName} sidecar to a {otel} sidecar.

diff --git a/modules/otel-migrating-from-jaeger-without-sidecars.adoc b/modules/otel-migrating-from-jaeger-without-sidecars.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="migrating-to-otel-from-jaeger-without-sidecars_{context}"]
-= Migrating without sidecars
+= Migrate without sidecars
 
 [role="_abstract"]
 You can migrate from the {JaegerShortName} to the {otel} without sidecar deployment.

diff --git a/modules/otel-migrating-overview.adoc b/modules/otel-migrating-overview.adoc
@@ -4,11 +4,22 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="otel-migrating-overview_{context}"]
-= Migration overview
+= About migration
 
 [role="_abstract"]
-If you are already using the {JaegerName} for your applications, you can migrate to the {otel}, which is based on the link:https://opentelemetry.io/[OpenTelemetry] open source project.
+Migration from the {JaegerShortName} to the {otel} requires configuring the OpenTelemetry Collector and your applications to report traces seamlessly. You can migrate sidecar and sidecarless deployments.
 
 The {otel} provides a set of APIs, libraries, agents, and instrumentation to facilitate observability in distributed systems. The OpenTelemetry Collector in the {otel} can ingest the Jaeger protocol, so you do not need to change the SDKs in your applications.
 
-Migration from the {JaegerShortName} to the {otel} requires configuring the OpenTelemetry Collector and your applications to report traces seamlessly. You can migrate sidecar and sidecarless deployments.
+[WARNING]
+====
+[subs="attributes+"]
+
+The deprecated {JaegerName} 3.5 was the last release of the {JaegerName} that Red Hat supported.
+
+All support and maintenance for the deprecated {JaegerName} 3.5 ended on November 3, 2025.
+
+If you still use {JaegerName}, you must migrate to the {OTelOperator} and the {TempoOperator} for distributed tracing collection and storage. For more information, see "Migrating" in the {otel} documentation, "Installing" in the {otel} documentation, and "Installing" in the {TempoName} documentation.
+
+For more information, see the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/7083722[Jaeger Deprecation and Removal in OpenShift].
+====