elastic · colleenmcginnis · Mar 21, 2025 · Mar 20, 2025 · Mar 20, 2025 · Mar 21, 2025
diff --git a/docs/docset.yml b/docs/docset.yml
diff --git a/docs/reference/getting-started.md b/docs/reference/getting-started.md
@@ -41,13 +41,13 @@ client = Elasticsearch(
 
 Your Elasticsearch endpoint can be found on the **My deployment** page of your deployment:
 
-:::{image} ../images/es-endpoint.jpg
+:::{image} images/es-endpoint.jpg
 :alt: Finding Elasticsearch endpoint
 :::
 
 You can generate an API key on the **Management** page under Security.
 
-:::{image} ../images/create-api-key.png
+:::{image} images/create-api-key.png
 :alt: Create API key
 :::
 

diff --git a/docs/images/create-api-key.png → docs/reference/images/create-api-key.png b/docs/images/create-api-key.png → docs/reference/images/create-api-key.png
diff --git a/docs/images/es-endpoint.jpg → docs/reference/images/es-endpoint.jpg b/docs/images/es-endpoint.jpg → docs/reference/images/es-endpoint.jpg
diff --git a/docs/images/otel-waterfall-retry.png → ...reference/images/otel-waterfall-retry.png b/docs/images/otel-waterfall-retry.png → ...reference/images/otel-waterfall-retry.png
diff --git a/docs/images/otel-waterfall-with-http.png → ...rence/images/otel-waterfall-with-http.png b/docs/images/otel-waterfall-with-http.png → ...rence/images/otel-waterfall-with-http.png
diff --git a/docs/images/otel-waterfall-without-http.png → ...ce/images/otel-waterfall-without-http.png b/docs/images/otel-waterfall-without-http.png → ...ce/images/otel-waterfall-without-http.png
diff --git a/docs/reference/opentelemetry.md b/docs/reference/opentelemetry.md
@@ -9,21 +9,21 @@ You can use [OpenTelemetry](https://opentelemetry.io/) to monitor the performanc
 
 The native instrumentation in the Python client follows the [OpenTelemetry Semantic Conventions for {{es}}](https://opentelemetry.io/docs/specs/semconv/database/elasticsearch/). In particular, the instrumentation in the client covers the logical layer of {{es}} requests. A single span per request is created that is processed by the service through the Python client. The following image shows a trace that records the handling of two different {{es}} requests: an `info` request and a `search` request.
 
-:::{image} ../images/otel-waterfall-without-http.png
+:::{image} images/otel-waterfall-without-http.png
 :alt: Distributed trace with Elasticsearch spans
 :class: screenshot
 :::
 
 Usually, OpenTelemetry auto-instrumentation modules come with instrumentation support for HTTP-level communication. In this case, in addition to the logical {{es}} client requests, spans will be captured for the physical HTTP requests emitted by the client. The following image shows a trace with both, {{es}} spans (in blue) and the corresponding HTTP-level spans (in red) after having installed the ``opentelemetry-instrumentation-urllib3`` package:
 
-:::{image} ../images/otel-waterfall-with-http.png
+:::{image} images/otel-waterfall-with-http.png
 :alt: Distributed trace with Elasticsearch spans
 :class: screenshot
 :::
 
 Advanced Python client behavior such as nodes round-robin and request retries are revealed through the combination of logical {{es}} spans and the physical HTTP spans. The following example shows a `search` request in a scenario with two nodes:
 
-:::{image} ../images/otel-waterfall-retry.png
+:::{image} images/otel-waterfall-retry.png
 :alt: Distributed trace with Elasticsearch spans
 :class: screenshot
 :::