fixing multiple links

Author: eedugon

deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md

@@ -24,7 +24,7 @@ Why this matters:
 ECH and ECE orchestators automatically handle several aspects of cluster resilience that are discussed in the self-managed resiliency guidance for [small](./resilience-in-small-clusters.md) and [large](./resilience-in-larger-clusters.md) clusters:
 
 * Configuring master-eligible nodes:
-  * Setting up a [voting-only tiebreaker](/distributed-architecture/clusters-nodes-shards/node-roles.md#voting-only-node) when the cluster spans to two availability zones.
+  * Setting up a [voting-only tiebreaker](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#voting-only-node) when the cluster spans to two availability zones.
   * Promoting [dedicated master nodes](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#dedicated-master-node) as the cluster grows to improve stability and fault tolerance.
 * Enabling [shard allocation awareness](../../distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md) to maintain resilience during whole-zone failures.
 * Automatically assigning [node roles](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md) based on the configured [data tiers](/manage-data/lifecycle/data-tiers.md).

deploy-manage/production-guidance/elasticsearch-in-production-environments.md

@@ -62,7 +62,7 @@ The following topics, covered in other sections of the documentation, offer valu
 ### Plan your data structure and formatting [ec_plan_your_data_structure_availability_and_formatting]
 
 * Build a [data architecture](/manage-data/lifecycle/data-tiers.md) that best fits your needs. Based on your own access and retention policies, you can add warm, cold, and frozen data tiers, and automate deletion of old data.
-* Normalize event data to better analyze, visualize, and correlate your events by adopting the [Elastic Common Schema](asciidocalypse://docs/ecs/docs/reference/ecs-getting-started.md) (ECS). Elastic integrations use ECS out-of-the-box. If you are writing your own integrations, ECS is recommended.
+* Normalize event data to better analyze, visualize, and correlate your events by adopting the [Elastic Common Schema](ecs://reference/ecs-getting-started.md) (ECS). Elastic integrations use ECS out-of-the-box. If you are writing your own integrations, ECS is recommended.
 * Once you have your data tiers deployed and you have data flowing, you can [manage the index lifecycle](/manage-data/lifecycle/index-lifecycle-management.md).
 
   ::::{tip}

deploy-manage/production-guidance/kibana-in-production-environments.md

@@ -1,7 +1,5 @@
 ---
 navigation_title: "Run Kibana in production"
-mapped_pages:
-  - https://www.elastic.co/guide/en/kibana/current/production.html
 applies_to:
   deployment:
     ess: all

deploy-manage/production-guidance/kibana-load-balance-traffic.md

@@ -1,5 +1,7 @@
 ---
 navigation_title: "High availability and load balancing"
+mapped_pages:
+  - https://www.elastic.co/guide/en/kibana/current/production.html
 applies_to:
   deployment:
     self: all
@@ -15,7 +17,7 @@ The configurations provided in this section are required only for self-managed d
 
 ## Load balancing across multiple {{kib}} instances [load-balancing-kibana]
 
-To run multiple {{kib}} instances connected to the same {{es}} cluster, you need to adjust the configuration. See the [{{kib}} configuration reference](kibana://reference/configuration-reference) for details on each setting.
+To run multiple {{kib}} instances connected to the same {{es}} cluster, you need to adjust the configuration. See the [{{kib}} configuration reference](kibana://reference/configuration-reference.md) for details on each setting.
 
 ::::{note}
 When adding multiple {{kib}} instances to the same deployment in {{ech}}, {{ece}}, or {{eck}}, the orchestrator applies the necessary configuration, requiring no manual setup.

deploy-manage/production-guidance/kibana-reporting-production-considerations.md

@@ -13,7 +13,7 @@ In production environments, it's important to ensure that Kibana reporting is bo
 
 Because this process requires launching a browser within your server environment, you should pay special attention to operating system compatibility, sandboxing, and dependencies.
 
-Chromium is an open-source project not related to Elastic, and is embedded into {{kib}} (except on Darwin). Running Chromium reliably may require [additional OS dependencies](/deploy-manage/deploy/kibana-reporting-configuration.md#install-reporting-packages) and proper sandbox configuration to protect your system from potential browser-level vulnerabilities.
+Chromium is an open-source project not related to Elastic, and is embedded into {{kib}} (except on Darwin). Running Chromium reliably may require [additional OS dependencies](/deploy-manage/kibana-reporting-configuration.md#install-reporting-packages) and proper sandbox configuration to protect your system from potential browser-level vulnerabilities.
 
 ::::{note} 
 Chromium is not embedded into {{kib}} for the Darwin (Mac OS) architecture. When running on Darwin, Reporting will download Chromium into the proper area of the {{kib}} installation path the first time the server starts. To separately download and install the browser, see [Manually install the Chromium browser for Darwin](../../explore-analyze/report-and-share/reporting-troubleshooting-pdf.md#reporting-manual-chromium-install).

troubleshoot/elasticsearch/security/trb-security-saml.md

@@ -175,7 +175,7 @@ Some of the common SAML problems are shown below with tips on how to resolve the
 
     For further information, please read [MDN SameSite cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite)
 
-    If you serve multiple {{kib}} installations behind a load balancer make sure to use the [same security configuration](/deploy-manage/production-guidance/kibana-in-production-environments.md#load-balancing-kibana) for all installations.
+    If you serve multiple {{kib}} installations behind a load balancer make sure to use the [same security configuration](/deploy-manage/production-guidance/kibana-load-balance-traffic.md#load-balancing-kibana) for all installations.
 
 
 **Logging:**