[docs] Miscellaneous docs clean up (#2604)

* remove unused substitutions

* move images

* fix image path

Author: colleenmcginnis

docs/docset.yml

@@ -16,7 +16,7 @@ This document contains code snippets to show you how to connect to various {{es}
 
 If you are using [Elastic Cloud](https://www.elastic.co/cloud), the client offers an easy way to connect to it. You need the Cloud ID that you can find in the cloud console, then your username and password.
 
-:::{image} ../images/cloud_id.png
+:::{image} images/cloud_id.png
 :alt: Cloud ID
 :::
 
@@ -34,19 +34,19 @@ client = Elasticsearch::Client.new(
 
 You can also connect to the Cloud by using API Key authentication. You can generate an `API key` in the `Management` page under the section `Security`.
 
-:::{image} ../images/cloud_api_key.png
+:::{image} images/cloud_api_key.png
 :alt: API key
 :::
 
 When you click on `Create API key` you can choose a name and set the other options (eg. restrict privileges, expire after time, etc).
 
-:::{image} ../images/api_key_name.png
+:::{image} images/api_key_name.png
 :alt: Choose an API name
 :::
 
 After this step you will get the `API key` in the API keys page.
 
-:::{image} ../images/cloud_api_key.png
+:::{image} images/cloud_api_key.png
 :alt: API key
 :::
 

docs/reference/connecting.md

@@ -38,13 +38,13 @@ client = Elasticsearch::Client.new(
 
 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
 :::
 

docs/reference/getting-started.md

@@ -9,21 +9,21 @@ You can use [OpenTelemetry](https://opentelemetry.io/) to monitor the performanc
 
 The native instrumentation in the Ruby 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 Ruby Client. The following image shows a trace that records the handling of two different {{es}} requests: a `ping` 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):
 
-:::{image} ../images/otel-waterfall-with-http.png
+:::{image} images/otel-waterfall-with-http.png
 :alt: Distributed trace with Elasticsearch spans
 :class: screenshot
 :::
 
 Advanced Ruby 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
 :::