fixes

Author: shainaraskas

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

@@ -17,7 +17,7 @@ This topic describes how to configure a self-managed {{es}} cluster. Other deplo
 
 To learn how to configure `elasticsearch.yml` for other deployment types, refer to [](/deploy-manage/stack-settings.md).
 
-JVM and log4j configuration is not available in all deployment types. To learn how to configure limited JVM options in {{eck}}, refer to [](deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md).
+JVM and log4j configuration is not available in all deployment types. To learn how to configure limited JVM options in {{eck}}, refer to [](/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md).
 :::
 
 ## Available settings

deploy-manage/stack-settings.md

@@ -34,7 +34,7 @@ The available {{stack}} settings differ depending on your deployment type.
 
 ### {{kib}} settings
 
-{{es}} settings can be found in the [{{kib}} configuration reference](kibana:///reference/configuration-reference/index.md).
+{{es}} settings can be found in the [{{kib}} configuration reference](kibana://reference/configuration-reference.md).
 
 | Deployment type | Applicable settings | 
 | --- | --- |
@@ -55,7 +55,7 @@ For APM and Enterprise Search, refer to the product's documentation:
 The way that you configure your {{stack}} settings is determined by your deployment type.
 
 :::{warning}
-* You can also update [dynamic {{es}} cluster settings](#dynamic-cluster-settings) using {{es}}'s [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). However, {{ech}} and {{ece}} don’t reject unsafe setting changes made using this API, and should be used with caution in these contexts.
+* You can also update [dynamic {{es}} cluster settings](#dynamic-cluster-setting) using {{es}}'s [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). However, {{ech}} and {{ece}} don’t reject unsafe setting changes made using this API, and should be used with caution in these contexts.
 * If a feature requires both standard `elasticsearch.yml` settings and [secure settings](/deploy-manage/security/secure-settings.md), configure the secure settings first. Updating standard user settings can trigger a cluster rolling restart in self managed clusters and ECH and ECE deployments. If the required secure settings are not yet in place, the nodes might fail to start. Adding secure settings does not trigger a restart.
 :::
 

solutions/security/detect-and-alert/detections-requirements.md

@@ -26,7 +26,7 @@ These steps are only required for **self-managed** deployments:
 
 * HTTPS must be configured for communication between [{{es}} and {{kib}}](/deploy-manage/security/set-up-basic-security-plus-https.md#encrypt-kibana-http).
 * In the `elasticsearch.yml` configuration file, set the `xpack.security.enabled` setting to `true`. For more information, refer to [Configuring {{es}}](/deploy-manage/deploy/self-managed/configure-elasticsearch.md) and [Security settings in {{es}}](elasticsearch://reference/elasticsearch/configuration-reference/security-settings.md).
-* In the `kibana.yml` [configuration file](kibana://reference/configuration-reference/index.md), add the `xpack.encryptedSavedObjects.encryptionKey` setting with any alphanumeric value of at least 32 characters. For example:
+* In [`kibana.yml`](/deploy-manage/stack-settings.md), add the `xpack.encryptedSavedObjects.encryptionKey` setting with any alphanumeric value of at least 32 characters. For example:
 
     `xpack.encryptedSavedObjects.encryptionKey: 'fhjskloppd678ehkdfdlliverpoolfcr'`