more

Author: shainaraskas

deploy-manage/deploy/self-managed/install-elasticsearch-docker-basic.md

@@ -12,7 +12,7 @@ navigation_title: Single-node cluster
 Use Docker commands to start a single-node {{es}} cluster for development or testing. You can then run additional Docker commands to add nodes to the test cluster or run {{kib}}.
 
 ::::{tip}
-* If you just want to test {{es}} in local development, refer to [Run {{es}} locally](../../../solutions/search/get-started.md). Please note that this setup is not suitable for production environments.
+* If you just want to test {{es}} in local development, refer to [Run {{es}} locally](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md). Please note that this setup is not suitable for production environments.
 * This setup doesn’t run multiple {{es}} nodes or {{kib}} by default. To create a multi-node cluster with {{kib}}, use Docker Compose instead. See [Start a multi-node cluster with Docker Compose](/deploy-manage/deploy/self-managed/install-elasticsearch-docker-compose.md).
 ::::
 

deploy-manage/deploy/self-managed/install-elasticsearch-docker-configure.md

@@ -13,7 +13,7 @@ When you run in Docker, the [{{es}} configuration files](configure-elasticsearch
 
 To use custom configuration files, you [bind-mount the files](#docker-config-bind-mount) over the configuration files in the image.
 
-You can set individual {{es}} configuration parameters using Docker environment variables. The [sample compose file](#docker-compose-file) and the [single-node example](#docker-cli-run-dev-mode) use this method. You can use the setting name directly as the environment variable name. If you cannot do this, for example because your orchestration platform forbids periods in environment variable names, then you can use an alternative style by converting the setting name as follows.
+You can set individual {{es}} configuration parameters using Docker environment variables. The [sample compose file](/deploy-manage/deploy/self-managed/install-elasticsearch-docker-compose.md) and the [single-node example](/deploy-manage/deploy/self-managed/install-elasticsearch-docker-basic.md) use this method. You can use the setting name directly as the environment variable name. If you can't do this, for example because your orchestration platform forbids periods in environment variable names, then you can use an alternative style by converting the setting name as follows:
 
 1. Change the setting name to uppercase
 2. Prefix it with `ES_SETTING_`
@@ -38,7 +38,7 @@ docker run <various parameters> bin/elasticsearch -Ecluster.name=mynewclusternam
 
 While bind-mounting your configuration files is usually the preferred method in production, you can also [create a custom Docker image](#_c_customized_image) that contains your configuration.
 
-### Mounting {{es}} configuration files [docker-config-bind-mount]
+## Mounting {{es}} configuration files [docker-config-bind-mount]
 
 Create custom config files and bind-mount them over the corresponding files in the Docker image. For example, to bind-mount `custom_elasticsearch.yml` with `docker run`, specify:
 
@@ -54,7 +54,7 @@ The container **runs {{es}} as user `elasticsearch` using uid:gid `1000:0`**. Bi
 
 
 
-### Create an encrypted {{es}} keystore [docker-keystore-bind-mount]
+## Create an encrypted {{es}} keystore [docker-keystore-bind-mount]
 
 By default, {{es}} will auto-generate a keystore file for [secure settings](../../security/secure-settings.md). This file is obfuscated but not encrypted.
 
@@ -91,7 +91,7 @@ If you’ve already created the keystore and don’t need to update it, you can
 ```
 
 
-### Using custom Docker images [_c_customized_image]
+## Using custom Docker images [_c_customized_image]
 
 In some environments, it might make more sense to prepare a custom image that contains your configuration. A `Dockerfile` to achieve this might be as simple as:
 
@@ -115,7 +115,7 @@ Some plugins require additional security permissions. You must explicitly accept
 See [Plugin management](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/_other_command_line_parameters.md) for more information.
 
 
-### Troubleshoot Docker errors for {{es}} [troubleshoot-docker-errors]
+## Troubleshoot Docker errors for {{es}} [troubleshoot-docker-errors]
 
 Here’s how to resolve common errors when running {{es}} with Docker.
 

deploy-manage/deploy/self-managed/install-elasticsearch-docker-prod.md

@@ -177,16 +177,20 @@ The `ES_JAVA_OPTS` variable overrides all other JVM options. We do not recommend
 
 ## Pin deployments to a specific image version [_pin_deployments_to_a_specific_image_version]
 
-Pin your deployments to a specific version of the {{es}} Docker image. For example `docker.elastic.co/elasticsearch/elasticsearch:{{stack-version}}`.
+Pin your deployments to a specific version of the {{es}} Docker image. For example:
+
+```sh
+docker.elastic.co/elasticsearch/elasticsearch:{{stack-version}}
+```
 
 
 ## Always bind data volumes [_always_bind_data_volumes]
 
 You should use a volume bound on `/usr/share/elasticsearch/data` for the following reasons:
 
-1. The data of your {{es}} node won’t be lost if the container is killed
-2. {{es}} is I/O sensitive and the Docker storage driver is not ideal for fast I/O
-3. It allows the use of advanced [Docker volume plugins](https://docs.docker.com/engine/extend/plugins/#volume-plugins)
+1. The data of your {{es}} node won’t be lost if the container is killed.
+2. {{es}} is I/O sensitive and the Docker storage driver is not ideal for fast I/O.
+3. It allows the use of advanced [Docker volume plugins](https://docs.docker.com/engine/extend/plugins/#volume-plugins).
 
 
 ## Avoid using `loop-lvm` mode [_avoid_using_loop_lvm_mode]

deploy-manage/deploy/self-managed/install-elasticsearch-with-docker.md

@@ -17,7 +17,7 @@ Docker images for {{es}} are available from the Elastic Docker registry. A list
 :::
 
 ::::{tip}
-If you just want to test {{es}} in local development, refer to [Run {{es}} locally](../../../solutions/search/get-started.md). Please note that this setup is not suitable for production environments.
+If you just want to test {{es}} in local development, refer to [Run {{es}} locally](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md). Please note that this setup is not suitable for production environments.
 ::::
 
 Review the following guides to install {{es}} with Docker:

deploy-manage/deploy/self-managed/installing-elasticsearch.md

@@ -68,7 +68,7 @@ If you want to install and manage {{es}} yourself, you can:
 * Run {{es}} in a [Docker container](/deploy-manage/deploy/self-managed/installing-elasticsearch.md#elasticsearch-docker-images).
 
 ::::{tip}
-To try out  on your own machine, we recommend using Docker and running both {{es}} and Kibana. For more information, see [Run {{es}} locally](../../../solutions/search/get-started.md). This setup is not suitable for production use.
+To try out  on your own machine, we recommend using Docker and running both {{es}} and Kibana. For more information, see [Run {{es}} locally](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md). This setup is not suitable for production use.
 ::::
 
 ## {{es}} install packages [elasticsearch-install-packages]