fixing anchor

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 [ec-ha]
 
 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
 
 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.
 
@@ -33,7 +33,7 @@ Moreover, a high availability (HA) cluster requires at least three master-eligib
 
 The data in your {{es}} clusters is also backed up every 30 minutes, 4 hours, or 24 hours, depending on which snapshot interval you choose. These regular intervals provide an extra level of redundancy. We do support [snapshot and restore](../../../deploy-manage/tools/snapshot-and-restore.md), regardless of whether you use one, two, or three availability zones. However, with only a single availability zone and in the event of an outage, it might take a while for your cluster come back online. Using a single availability zone also leaves your cluster exposed to the risk of data loss, if the backups you need are not useable (failed or partial snapshots missing the indices to restore) or no longer available by the time that you realize that you might need the data (snapshots have a retention policy).
 
-### Important considerations
+## Important considerations
 
 ::::{warning} 
 * Clusters that use only one availability zone are not highly available and are at risk of data loss. To safeguard against data loss, you must use at least two availability zones.