errors batch

Author: shainaraskas

deploy-manage/deploy/self-managed/_snippets/auto-security-config.md

@@ -1,12 +1,12 @@
 When you start {{es}} for the first time, the following security configuration occurs automatically:
 
-* [Certificates and keys](../../../deploy-manage/security/security-certificates-keys.md#stack-security-certificates) for TLS are generated for the transport and HTTP layers.
+* [Certificates and keys](/deploy-manage/security/security-certificates-keys.md#stack-security-certificates) for TLS are generated for the transport and HTTP layers.
 * The TLS configuration settings are written to `elasticsearch.yml`.
 * A password is generated for the `elastic` user.
 * An enrollment token is generated for {{kib}}, which is valid for 30 minutes.
 
 You can then start {{kib}} and enter the enrollment token. This token automatically applies the security settings from your {{es}} cluster, authenticates to {{es}} with the built-in `kibana` service account, and writes the security configuration to `kibana.yml`.
 
 ::::{note}
-There are [some cases](../../../deploy-manage/security/security-certificates-keys.md#stack-skip-auto-configuration) where security can’t be configured automatically because the node startup process detects that the node is already part of a cluster, or that security is already configured or explicitly disabled.
+There are [some cases](/deploy-manage/security/security-certificates-keys.md#stack-skip-auto-configuration) where security can’t be configured automatically because the node startup process detects that the node is already part of a cluster, or that security is already configured or explicitly disabled.
 ::::

deploy-manage/deploy/self-managed/_snippets/install-next-steps.md

@@ -1,5 +1,5 @@
 You now have a test {{es}} environment set up. Before you start serious development or go into production with {{es}}, you must do some additional setup:
 
-* Learn how to [configure {{es}}](configure-elasticsearch.md).
-* Configure [important {{es}} settings](important-settings-configuration.md).
-* Configure [important system settings](important-system-configuration.md).
+* Learn how to [configure {{es}}](/deploy-manage/deploy/self-managed/configure-elasticsearch.md).
+* Configure [important {{es}} settings](/deploy-manage/deploy/self-managed/important-settings-configuration.md).
+* Configure [important system settings](/deploy-manage/deploy/self-managed/important-system-configuration.md).

deploy-manage/deploy/self-managed/_snippets/java-version.md

@@ -1,3 +1,3 @@
 ::::{note}
-{{es}} includes a bundled version of [OpenJDK](https://openjdk.java.net) from the JDK maintainers (GPLv2+CE). To use your own version of Java, see the [JVM version requirements](installing-elasticsearch.md#jvm-version).
+{{es}} includes a bundled version of [OpenJDK](https://openjdk.java.net) from the JDK maintainers (GPLv2+CE). To use your own version of Java, see the [JVM version requirements](/deploy-manage/deploy/self-managed/installing-elasticsearch.md#jvm-version).
 ::::

deploy-manage/deploy/self-managed/_snippets/pw-env-var.md

@@ -6,6 +6,6 @@ We recommend storing the `elastic` password as an environment variable in your s
 {{export}}ELASTIC_PASSWORD="your_password"
 ```
 
-If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](../../security/secure-settings.md) for more details.
+If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](/deploy-manage/security/secure-settings.md) for more details.
 
 To learn how to reset this password, refer to [](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md).

deploy-manage/deploy/self-managed/_snippets/security-files.md

@@ -9,7 +9,7 @@ When you install {{es}}, the following certificates and keys are generated in th
 `transport.p12`
 :   Keystore that contains the key and certificate for the transport layer for all the nodes in your cluster.
 
-`http.p12` and `transport.p12` are password-protected PKCS#12 keystores. {{es}} stores the passwords for these keystores as [secure settings](../../security/secure-settings.md). To retrieve the passwords so that you can inspect or change the keystore contents, use the [`bin/elasticsearch-keystore`](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md) tool.
+`http.p12` and `transport.p12` are password-protected PKCS#12 keystores. {{es}} stores the passwords for these keystores as [secure settings](/deploy-manage/security/secure-settings.md). To retrieve the passwords so that you can inspect or change the keystore contents, use the [`bin/elasticsearch-keystore`](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/command-line-tools/elasticsearch-keystore.md) tool.
 
 Use the following command to retrieve the password for `http.p12`:
 

deploy-manage/deploy/self-managed/_snippets/start-local.md

@@ -1,7 +1,7 @@
 ::::{warning}
 **DO NOT USE THESE INSTRUCTIONS FOR PRODUCTION DEPLOYMENTS**
 
-The instructions on this page are for **local development only**. Do not use this configuration for production deployments, because it is not secure. Refer to [deployment options](../../get-started/deployment-options.md) for a list of production deployment options.
+The instructions on this page are for **local development only**. Do not use this configuration for production deployments, because it is not secure. Refer to [](/get-started/deployment-options.md) for a list of production deployment options.
 
 ::::
 

deploy-manage/deploy/self-managed/_snippets/targz-daemon.md

@@ -4,7 +4,7 @@ To run {{es}} as a daemon, specify `-d` on the command line, and record the proc
 ./bin/elasticsearch -d -p pid
 ```
 
-If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](../../security/secure-settings.md) for more details.
+If you have password-protected the {{es}} keystore, you will be prompted to enter the keystore’s password. See [Secure settings](/deploy-manage/security/secure-settings.md) for more details.
 
 Log messages can be found in the `$ES_HOME/logs/` directory.
 
@@ -15,5 +15,5 @@ pkill -F pid
 ```
 
 ::::{note}
-The {{es}} `.tar.gz` package does not include the `systemd` module. To manage {{es}} as a service, use the [Debian](../../maintenance/start-stop-services/start-stop-elasticsearch.md#start-deb) or [RPM](../../maintenance/start-stop-services/start-stop-elasticsearch.md#start-rpm) package instead.
+The {{es}} `.tar.gz` package does not include the `systemd` module. To manage {{es}} as a service, use the [Debian](/deploy-manage/deploy/self-managed/install-with-debian-package.md) or [RPM](/deploy-manage/deploy/self-managed/install-with-rpm.md) package instead.
 ::::

deploy-manage/deploy/self-managed/_snippets/targz-start.md

@@ -3,7 +3,7 @@ Run the following command to start {{es}} from the command line:
 ```sh
 ./bin/elasticsearch
 ```
-By default, {{es}} prints its logs to the console (`stdout`) and to the `<cluster name>.log` file within the [logs directory](important-settings-configuration.md#path-settings). {{es}} logs some information while it is starting, but after it has finished initializing it will continue to run in the foreground and won’t log anything further until something happens that is worth recording. While {{es}} is running you can interact with it through its HTTP interface which is on port `9200` by default.
+By default, {{es}} prints its logs to the console (`stdout`) and to the `<cluster name>.log` file within the [logs directory](/deploy-manage/deploy/self-managed/important-settings-configuration.md#path-settings). {{es}} logs some information while it is starting, but after it has finished initializing it will continue to run in the foreground and won’t log anything further until something happens that is worth recording. While {{es}} is running you can interact with it through its HTTP interface which is on port `9200` by default.
 
 To stop {{es}}, press `Ctrl-C`.
 

deploy-manage/deploy/self-managed/_snippets/zip-windows-start.md

@@ -4,6 +4,6 @@ Run the following command to start {{es}} from the command line:
 .\bin\elasticsearch.bat
 ```
 
-By default {{es}} prints its logs to the console (`STDOUT`) and to the `<cluster name>.log` file within the [logs directory](important-settings-configuration.md#path-settings). {{es}} logs some information while it is starting, but after it has finished initializing it will continue to run in the foreground and won’t log anything further until something happens that is worth recording. While {{es}} is running you can interact with it through its HTTP interface which is on port `9200` by default.
+By default {{es}} prints its logs to the console (`STDOUT`) and to the `<cluster name>.log` file within the [logs directory](/deploy-manage/deploy/self-managed/important-settings-configuration.md#path-settings). {{es}} logs some information while it is starting, but after it has finished initializing it will continue to run in the foreground and won’t log anything further until something happens that is worth recording. While {{es}} is running you can interact with it through its HTTP interface which is on port `9200` by default.
 
 To stop {{es}}, press `Ctrl-C`.

deploy-manage/deploy/self-managed/bootstrap-checks.md

@@ -103,7 +103,7 @@ To pass the maximum size virtual memory check, you must configure your system to
 
 $$$bootstrap-checks-max-map-count$$$
 
-Continuing from the previous [point](max-size-virtual-memory-check.md), to use `mmap` effectively, {{es}} also requires the ability to create many memory-mapped areas. The maximum map count check checks that the kernel allows a process to have at least 262,144 memory-mapped areas and is enforced on Linux only. 
+In addition to [unlimited address space](#max-size-virtual-memory-check), to use `mmap` effectively, {{es}} also requires the ability to create many memory-mapped areas. The maximum map count check checks that the kernel allows a process to have at least 262,144 memory-mapped areas and is enforced on Linux only. 
 
 To pass the maximum map count check, you must configure `vm.max_map_count` via `sysctl` to be at least `262144`.
 
@@ -174,7 +174,7 @@ This bootstrap check ensures that discovery is not running with the default conf
 * `discovery.seed_providers`
 * `cluster.initial_master_nodes`
 
-Note that you must [remove `cluster.initial_master_nodes` from the configuration of every node](important-settings-configuration.md#initial_master_nodes) after the cluster has started for the first time. Instead, configure `discovery.seed_hosts` or `discovery.seed_providers`. If you do not need any discovery configuration, for instance if running a single-node cluster, set `discovery.seed_hosts: []` to disable discovery and satisfy this bootstrap check.
+Note that you must [remove `cluster.initial_master_nodes` from the configuration of every node](/deploy-manage/deploy/self-managed/important-settings-configuration.md#initial_master_nodes) after the cluster has started for the first time. Instead, configure `discovery.seed_hosts` or `discovery.seed_providers`. If you do not need any discovery configuration, for instance if running a single-node cluster, set `discovery.seed_hosts: []` to disable discovery and satisfy this bootstrap check.
 :::
 
 :::{dropdown} Encrypt sensitive data check