fixing ec-ha links and anchors

Author: eedugon

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

@@ -5,7 +5,7 @@ applies_to:
     ess: all
 ---
 
-# Resiliency in Elastic Cloud Hosted deployments [ec-ha]
+# Resiliency in Elastic Cloud Hosted deployments
 
 With {{ech}}, your deployment can be spread across up to three separate availability zones, each hosted in an isolated infrastructure domain, such as separate data centers in the case of {{ech}}.
 
@@ -19,7 +19,7 @@ Why this matters:
 * Multiple availability zones help your deployment remain available. This includes your {{es}} cluster, provided that your cluster is sized so that it can sustain your workload on the remaining data centers and that your indices are configured to have at least one replica.
 * Multiple availability zones enable you to perform changes to resize your deployment with zero downtime.
 
-## Recommendations
+## Recommendations [ec-ha]
 
 We recommend that you use at least two availability zones for production and three for mission-critical systems. Just one zone might be sufficient, if your {{es}} cluster is mainly used for testing or development and downtime is acceptable, but should never be used for production.
 

troubleshoot/monitoring/deployment-health-warnings.md

@@ -16,7 +16,7 @@ The {{ecloud}} [Deployments](https://cloud.elastic.co/deployments) page shows th
 
 **Seeing only one warning?**
 
-To resolve a single health warning, we recommended first re-applying any pending changes: Select **Edit** in the deployment menu to open the Edit page and then click **Save** without making any changes. This will check all components for pending changes and will apply the changes as needed. This may impact the uptime of clusters which are not [highly available](/deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md#ec-ha).
+To resolve a single health warning, we recommended first re-applying any pending changes: Select **Edit** in the deployment menu to open the Edit page and then click **Save** without making any changes. This will check all components for pending changes and will apply the changes as needed. This may impact the uptime of clusters which are not [highly available](/deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md).
 
 Re-saving the deployment configuration without making any changes is often all that’s needed to resolve a transient health warning on the UI. Saving will redirect you to the {{ech}} deployment [Activity page](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) where you can monitor plan completion. Repeat errors should be investigated; for more information refer to [resolving configuration change errors](/troubleshoot/monitoring/node-bootlooping.md).
 

troubleshoot/monitoring/high-availability.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 % TODO: Edit edit edit
 
-You created a new {{ech}} deployment that uses three availability zones and index replicas, because you want to use the [cluster for production](/deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md#ec-ha). It’s a mission-critical deployment and you need it to be able to handle user requests at all times. Your cluster has been up and running for some time and it seems to handle its workload well. But is this cluster really highly available, given its current workload?
+You created a new {{ech}} deployment that uses three availability zones and index replicas, because you want to use the [cluster for production](/deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md). It’s a mission-critical deployment and you need it to be able to handle user requests at all times. Your cluster has been up and running for some time and it seems to handle its workload well. But is this cluster really highly available, given its current workload?
 
 To answer this question, let’s take a look at CPU usage in the **Cluster Performance Metrics** section in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body):