diff --git a/modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc b/modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc
similarity index 97%
rename from modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc
rename to modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc
index 4ebcc51f6d..e9a398fcf9 100644
--- a/modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc
+++ b/modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc
@@ -6,7 +6,7 @@
 // * serverless/observability/tracing/serverless-tracing.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="distr-tracing-tempo-key-concepts-of-distributed-tracing_{context}"]
+[id="distr-tracing-tempo-key-concepts-in-distributed-tracing_{context}"]
 = Key concepts in distributed tracing
 
 Every time a user takes an action in an application, a request is executed by the architecture that may require dozens of different services to participate to produce a response.
diff --git a/observability/distr_tracing/distr-tracing-architecture.adoc b/observability/distr_tracing/distr-tracing-architecture.adoc
index 3c93bbb3c6..b9fc5f0745 100644
--- a/observability/distr_tracing/distr-tracing-architecture.adoc
+++ b/observability/distr_tracing/distr-tracing-architecture.adoc
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-include::modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc[leveloffset=+1]
+include::modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
diff --git a/serverless/observability/tracing/serverless-tracing.adoc b/serverless/observability/tracing/serverless-tracing.adoc
index 0293709ef3..8406a31c5b 100644
--- a/serverless/observability/tracing/serverless-tracing.adoc
+++ b/serverless/observability/tracing/serverless-tracing.adoc
@@ -10,7 +10,7 @@ toc::[]
 Distributed tracing records the path of a request through the various services that make up an application. It is used to tie information about different units of work together, to understand a whole chain of events in a distributed transaction. The units of work might be executed in different processes or hosts.
 
 ifdef::openshift-enterprise[]
-include::modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc[leveloffset=+1]
+include::modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc[leveloffset=+1]
 endif::[]
 
 ifdef::openshift-enterprise[]
diff --git a/service_mesh/v1x/ossm-architecture.adoc b/service_mesh/v1x/ossm-architecture.adoc
index 53c6e4c124..3404c95936 100644
--- a/service_mesh/v1x/ossm-architecture.adoc
+++ b/service_mesh/v1x/ossm-architecture.adoc
@@ -38,7 +38,7 @@ Jaeger records the execution of individual requests across the whole stack of mi
 
 A *span* represents a logical unit of work in Jaeger that has an operation name, the start time of the operation, and the duration. Spans may be nested and ordered to model causal relationships.
 
-include::modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc[leveloffset=+2]
+include::modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc[leveloffset=+2]
 
 include::modules/jaeger-architecture.adoc[leveloffset=+2]
 
diff --git a/service_mesh/v2x/ossm-architecture.adoc b/service_mesh/v2x/ossm-architecture.adoc
index b56220d2b8..980c5c4e53 100644
--- a/service_mesh/v2x/ossm-architecture.adoc
+++ b/service_mesh/v2x/ossm-architecture.adoc
@@ -37,7 +37,7 @@ The {JaegerShortName} records the execution of individual requests across the wh
 
 A *span* represents a logical unit of work that has an operation name, the start time of the operation, and the duration. Spans may be nested and ordered to model causal relationships.
 
-include::modules/distr-tracing-tempo-key-concepts-of-distributed-tracing.adoc[leveloffset=+2]
+include::modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc[leveloffset=+2]
 
 include::modules/distr-tracing-architecture.adoc[leveloffset=+2]