more errors

Author: shainaraskas

deploy-manage/deploy/cloud-on-k8s/create-custom-images.md

@@ -50,7 +50,7 @@ If your custom images follow the naming convention adopted by the official image
 
 For more information, check the following references:
 
-* [Elasticsearch documentation on Using custom Docker images](/deploy-manage/deploy/self-managed/install-elasticsearch-with-docker.md#_c_customized_image)
+* [Elasticsearch documentation on Using custom Docker images](/deploy-manage/deploy/self-managed/install-elasticsearch-docker-configure.md#_c_customized_image)
 * [Google Container Registry](https://cloud.google.com/container-registry/docs/how-to)
 * [Azure Container Registry](https://docs.microsoft.com/en-us/azure/container-registry/)
 * [Amazon Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.md)

deploy-manage/deploy/self-managed/important-settings-configuration.md

@@ -134,7 +134,7 @@ If your master-eligible nodes do not have fixed names or addresses, use an [alte
 
 ### `cluster.initial_master_nodes` [initial_master_nodes]
 
-When you start an {{es}} cluster for the first time, a [cluster bootstrapping](../../distributed-architecture/discovery-cluster-formation/modules-discovery-bootstrap-cluster.md) step determines the set of master-eligible nodes whose votes are counted in the first election. In [development mode](/deploy-manage/deploy/self-managed/bootstrap-checks.md#bootstrap-checks.md#dev-vs-prod-mode), with no discovery settings configured, this step is performed automatically by the nodes themselves.
+When you start an {{es}} cluster for the first time, a [cluster bootstrapping](../../distributed-architecture/discovery-cluster-formation/modules-discovery-bootstrap-cluster.md) step determines the set of master-eligible nodes whose votes are counted in the first election. In [development mode](/deploy-manage/deploy/self-managed/bootstrap-checks.md#dev-vs-prod-mode), with no discovery settings configured, this step is performed automatically by the nodes themselves.
 
 Because auto-bootstrapping is [inherently unsafe](../../distributed-architecture/discovery-cluster-formation/modules-discovery-quorums.md), when starting a new cluster in production mode, you must explicitly list the master-eligible nodes whose votes should be counted in the very first election. You set this list using the `cluster.initial_master_nodes` setting on every master-eligible node. Do not configure this setting on master-ineligible nodes.
 

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

@@ -66,7 +66,7 @@ Use Docker commands to start a single-node {{es}} cluster for development or tes
     ```
 
     ::::{tip}
-    Use the `-m` flag to set a memory limit for the container. This removes the need to [manually set the JVM size](#docker-set-heap-size).
+    Use the `-m` flag to set a memory limit for the container. This removes the need to [manually set the JVM size](/deploy-manage/deploy/self-managed/install-elasticsearch-docker-prod.md#docker-set-heap-size).
     ::::
 
 

deploy-manage/maintenance/start-stop-services/start-stop-elasticsearch.md

@@ -122,7 +122,7 @@ To avoid this, upgrade your `systemd` to at least version 238. You can also temp
 
 ### Docker images [start-docker]
 
-If you installed a Docker image, you can start {{es}} from the command line. There are different methods depending on whether you’re using development mode or production mode. See [Run {{es}} in Docker](../../../deploy-manage/deploy/self-managed/install-elasticsearch-with-docker.md#docker-cli-run-dev-mode).
+If you installed a Docker image, you can start {{es}} from the command line. There are different methods depending on whether you’re using development mode or production mode. See [](../../../deploy-manage/deploy/self-managed/install-elasticsearch-with-docker.md).
 
 ### RPM packages [start-rpm]
 

raw-migrated-files/elasticsearch/elasticsearch-reference/security-basic-setup.md

@@ -8,7 +8,7 @@ navigation_title: "Set up basic security"
 When you start {{es}} for the first time, passwords are generated for the `elastic` user and TLS is automatically configured for you. If you configure security manually *before* starting your {{es}} nodes, the auto-configuration process will respect your security configuration. You can adjust your TLS configuration at any time, such as [updating node certificates](../../../deploy-manage/security/updating-certificates.md).
 
 ::::{important}
-If your cluster has multiple nodes, then you must configure TLS between nodes. [Production mode](bootstrap-checks.md#dev-vs-prod-mode) clusters will not start if you do not enable TLS.
+If your cluster has multiple nodes, then you must configure TLS between nodes. [Production mode](/deploy-manage/deploy/self-managed/bootstrap-checks.md#dev-vs-prod-mode) clusters will not start if you do not enable TLS.
 ::::