fixed 3 links

Author: eedugon

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

@@ -48,4 +48,4 @@ Depending on your needs and budget, an {{es}} cluster can consist of a single no
 
 * [Resilience in small clusters](availability-and-resilience/resilience-in-small-clusters.md)
 * [Resilience in larger clusters](availability-and-resilience/resilience-in-larger-clusters.md)
-* [Resilience in {{ech}} deployments](./availability-and-resilience/resiliente-in-ech.md)
+* [Resilience in {{ech}} deployments](./availability-and-resilience/resilience-in-ech.md)

deploy-manage/production-guidance/scaling-considerations.md

@@ -22,7 +22,7 @@ To make informed scaling decisions, [cluster monitoring](/deploy-manage/monitor.
 
 ## Performance optimizations and scaling
 
-Scaling isn’t just about adding more nodes—it also involves [optimizing the cluster configuration for better performance](./production-guidance/optimize-performance.md). Adjustments such as shard and index tuning, query optimizations, caching strategies, and efficient resource allocation can improve performance without requiring additional hardware. These optimizations directly influence scaling strategies, as a well-tuned cluster can handle more workload with fewer resources.
+Scaling isn’t just about adding more nodes—it also involves [optimizing the cluster configuration for better performance](./optimize-performance.md). Adjustments such as shard and index tuning, query optimizations, caching strategies, and efficient resource allocation can improve performance without requiring additional hardware. These optimizations directly influence scaling strategies, as a well-tuned cluster can handle more workload with fewer resources.
 
 ## Scaling and fault tolerance
 

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.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#ec-ha).
 
 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.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#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?
 
 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):