From 8ef63123ccec70c8693d228cf67dd8fc245e2df4 Mon Sep 17 00:00:00 2001
From: Marci W <333176+marciw@users.noreply.github.com>
Date: Mon, 24 Mar 2025 11:17:52 -0400
Subject: [PATCH 1/2] undo overeager edit; make phrasing consistent

---
 troubleshoot/elasticsearch.md                                   | 2 +-
 troubleshoot/elasticsearch/circuit-breaker-errors.md            | 2 +-
 troubleshoot/elasticsearch/diagnose-unassigned-shards.md        | 2 +-
 troubleshoot/elasticsearch/diagnostic.md                        | 2 +-
 troubleshoot/elasticsearch/fix-common-cluster-issues.md         | 2 +-
 troubleshoot/elasticsearch/fix-watermark-errors.md              | 2 +-
 troubleshoot/elasticsearch/high-cpu-usage.md                    | 2 +-
 troubleshoot/elasticsearch/high-jvm-memory-pressure.md          | 2 +-
 troubleshoot/elasticsearch/hotspotting.md                       | 2 +-
 troubleshoot/elasticsearch/increase-cluster-shard-limit.md      | 2 +-
 troubleshoot/elasticsearch/increase-shard-limit.md              | 2 +-
 troubleshoot/elasticsearch/increase-tier-capacity.md            | 2 +-
 troubleshoot/elasticsearch/red-yellow-cluster-status.md         | 2 +-
 troubleshoot/elasticsearch/rejected-requests.md                 | 2 +-
 troubleshoot/elasticsearch/repeated-snapshot-failures.md        | 2 +-
 .../elasticsearch/troubleshooting-shards-capacity-issues.md     | 2 +-
 .../elasticsearch/troubleshooting-unbalanced-cluster.md         | 2 +-
 troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md  | 2 +-
 troubleshoot/monitoring/cluster-response-time.md                | 2 +-
 troubleshoot/monitoring/deployment-health-warnings.md           | 2 +-
 troubleshoot/monitoring/high-availability.md                    | 2 +-
 troubleshoot/monitoring/high-memory-pressure.md                 | 2 +-
 troubleshoot/monitoring/node-bootlooping.md                     | 2 +-
 troubleshoot/monitoring/performance.md                          | 2 +-
 troubleshoot/monitoring/unavailable-nodes.md                    | 2 +-
 troubleshoot/monitoring/unavailable-shards.md                   | 2 +-
 26 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/troubleshoot/elasticsearch.md b/troubleshoot/elasticsearch.md
index bdcbcd70f6..0ce1787233 100644
--- a/troubleshoot/elasticsearch.md
+++ b/troubleshoot/elasticsearch.md
@@ -9,7 +9,7 @@ mapped_pages:
 This section helps you fix issues with {{es}} deployments.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 ## General [troubleshooting-general]
diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md
index b33426414d..cc4b1032b2 100644
--- a/troubleshoot/elasticsearch/circuit-breaker-errors.md
+++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md
@@ -12,7 +12,7 @@ By default, the [parent circuit breaker](elasticsearch://reference/elasticsearch
 See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough of diagnosing circuit breaker errors.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
index 18731a468b..5ac9c7fe4d 100644
--- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
+++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
@@ -234,7 +234,7 @@ For more guidance on fixing the most common causes for unassinged shards please
 See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 ## Common issues
diff --git a/troubleshoot/elasticsearch/diagnostic.md b/troubleshoot/elasticsearch/diagnostic.md
index 6ff4b85f0e..66bc5b8111 100644
--- a/troubleshoot/elasticsearch/diagnostic.md
+++ b/troubleshoot/elasticsearch/diagnostic.md
@@ -16,7 +16,7 @@ You can generate diagnostic information using this tool before you contact [Elas
 See this [this video](https://www.youtube.com/watch?v=Bb6SaqhqYHw) for a walkthrough of capturing an {{es}} diagnostic.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/fix-common-cluster-issues.md b/troubleshoot/elasticsearch/fix-common-cluster-issues.md
index fd322cc267..d5038cd4b0 100644
--- a/troubleshoot/elasticsearch/fix-common-cluster-issues.md
+++ b/troubleshoot/elasticsearch/fix-common-cluster-issues.md
@@ -9,7 +9,7 @@ mapped_pages:
 Use these topics to fix common issues with {{es}} clusters.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md
index ff93800508..b8e45c8436 100644
--- a/troubleshoot/elasticsearch/fix-watermark-errors.md
+++ b/troubleshoot/elasticsearch/fix-watermark-errors.md
@@ -16,7 +16,7 @@ To prevent a full disk, when a node reaches this watermark, {{es}} [blocks write
 {{es}} will automatically remove the write block when the affected node’s disk usage falls below the [high disk watermark](elasticsearch://reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings.md#cluster-routing-watermark-high). To achieve this, {{es}} attempts to rebalance some of the affected node’s shards to other nodes in the same data tier.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md
index 6d6e7df5eb..321bdcf06e 100644
--- a/troubleshoot/elasticsearch/high-cpu-usage.md
+++ b/troubleshoot/elasticsearch/high-cpu-usage.md
@@ -13,7 +13,7 @@ If a thread pool is depleted, {{es}} will [reject requests](rejected-requests.md
 You might experience high CPU usage if a [data tier](../../manage-data/lifecycle/data-tiers.md), and therefore the nodes assigned to that tier, is experiencing more traffic than other tiers. This imbalance in resource utilization is also known as [hot spotting](hotspotting.md).
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
index 1c00b09b62..f44ee27df1 100644
--- a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
+++ b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md
@@ -8,7 +8,7 @@ mapped_pages:
 High JVM memory usage can degrade cluster performance and trigger [circuit breaker errors](circuit-breaker-errors.md). To prevent this, we recommend taking steps to reduce memory pressure if a node’s JVM memory usage consistently exceeds 85%.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/hotspotting.md b/troubleshoot/elasticsearch/hotspotting.md
index 1188eeb471..a6d6102dde 100644
--- a/troubleshoot/elasticsearch/hotspotting.md
+++ b/troubleshoot/elasticsearch/hotspotting.md
@@ -12,7 +12,7 @@ mapped_pages:
 Computer [hot spotting](https://en.wikipedia.org/wiki/Hot_spot_(computer_programming)) may occur in {{es}} when resource utilizations are unevenly distributed across [nodes](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md). Temporary spikes are not usually considered problematic, but ongoing significantly unique utilization may lead to cluster bottlenecks and should be reviewed.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
index 4655919eb0..a53acbdb89 100644
--- a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
+++ b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
@@ -129,5 +129,5 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec
 
 :::::::
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md
index c470e4f8bd..7698c9aa6c 100644
--- a/troubleshoot/elasticsearch/increase-shard-limit.md
+++ b/troubleshoot/elasticsearch/increase-shard-limit.md
@@ -128,5 +128,5 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec
 ::::::
 
 :::{tip}}
-If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md
index da59b5ec79..0cbab4d2b9 100644
--- a/troubleshoot/elasticsearch/increase-tier-capacity.md
+++ b/troubleshoot/elasticsearch/increase-tier-capacity.md
@@ -206,5 +206,5 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec
 
 :::::::
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
diff --git a/troubleshoot/elasticsearch/red-yellow-cluster-status.md b/troubleshoot/elasticsearch/red-yellow-cluster-status.md
index ed68a28924..7e752ed11f 100644
--- a/troubleshoot/elasticsearch/red-yellow-cluster-status.md
+++ b/troubleshoot/elasticsearch/red-yellow-cluster-status.md
@@ -16,7 +16,7 @@ When your cluster has a red or yellow health status, it will continue to process
 In many cases, your cluster will recover to green health status automatically. If the cluster doesn’t automatically recover, then you must [manually address](#fix-red-yellow-cluster-status) the remaining problems so management and cleanup activities can proceed. See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/rejected-requests.md b/troubleshoot/elasticsearch/rejected-requests.md
index f7a7e4ad26..fc66ffd964 100644
--- a/troubleshoot/elasticsearch/rejected-requests.md
+++ b/troubleshoot/elasticsearch/rejected-requests.md
@@ -12,7 +12,7 @@ When {{es}} rejects a request, it stops the operation and returns an error with
 * High [indexing pressure](elasticsearch://reference/elasticsearch/index-settings/pressure.md) that exceeds the [`indexing_pressure.memory.limit`](elasticsearch://reference/elasticsearch/index-settings/pressure.md#memory-limits).
 
 ::::{tip}
-If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 
 ::::
 
diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
index 3a35176a1b..9e7a6de7ee 100644
--- a/troubleshoot/elasticsearch/repeated-snapshot-failures.md
+++ b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
@@ -167,5 +167,5 @@ In the event that snapshots are failing for other reasons check the logs on the
 
 :::::::
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
index a50ead528c..abbabb43fb 100644
--- a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
+++ b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
@@ -426,5 +426,5 @@ PUT _cluster/settings
 
 :::::::
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md
index 7713c8de26..27b0694d57 100644
--- a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md
+++ b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md
@@ -15,7 +15,7 @@ Elasticsearch balances shards across data tiers to achieve a good compromise bet
 * write load (for indices in data streams)
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md
index 1d186505d3..f2f3a43344 100644
--- a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md
+++ b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md
@@ -15,7 +15,7 @@ Normally, a node will only leave a cluster if deliberately shut down. If a node
 * The master may appear busy due to frequent cluster state updates.
 
 ::::{tip}
-If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection and resolution. For more information, refer to [](/deploy-manage/monitor/autoops.md).
+If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
 ::::
 
 
diff --git a/troubleshoot/monitoring/cluster-response-time.md b/troubleshoot/monitoring/cluster-response-time.md
index 955bdedae7..6faa84dd9a 100644
--- a/troubleshoot/monitoring/cluster-response-time.md
+++ b/troubleshoot/monitoring/cluster-response-time.md
@@ -22,5 +22,5 @@ So what caused the sudden increase in response times? The key to the puzzle lies
 This cluster was sized to handle a certain number of user requests. As the user requests exceeded the maximum throughput that a cluster of this size could sustain, response times increased. To avoid such a slowdown, you either need to control the volume of user requests that reaches the {{es}} cluster or you need to size your cluster to be able to accommodate a sudden increase in user requests.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/deployment-health-warnings.md b/troubleshoot/monitoring/deployment-health-warnings.md
index d4f646dbe1..ae58116616 100644
--- a/troubleshoot/monitoring/deployment-health-warnings.md
+++ b/troubleshoot/monitoring/deployment-health-warnings.md
@@ -29,5 +29,5 @@ If multiple health warnings appear for one of your deployments, or if your deplo
 If the warning refers to a system change, check the deployment’s [Activity](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) page.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/high-availability.md b/troubleshoot/monitoring/high-availability.md
index eeea64512d..b8352c46f4 100644
--- a/troubleshoot/monitoring/high-availability.md
+++ b/troubleshoot/monitoring/high-availability.md
@@ -24,5 +24,5 @@ This CPU usage graph indicates that your cluster is load-balancing between the n
 Even if your cluster is performing well, you still need to make sure that there is sufficient spare capacity to deal with the outage of an entire availability zone. For this cluster to remain highly available at all times, you either need to increase its size or reduce its workload.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/high-memory-pressure.md b/troubleshoot/monitoring/high-memory-pressure.md
index 6ecf176c87..6f680d1d6b 100644
--- a/troubleshoot/monitoring/high-memory-pressure.md
+++ b/troubleshoot/monitoring/high-memory-pressure.md
@@ -30,7 +30,7 @@ In our example, the **Index Response Times** metric shows that high memory press
 If the performance impact from high memory pressure is not acceptable, you need to increase the cluster size or reduce the workload.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 ## Increase the deployment size [ec_increase_the_deployment_size]
diff --git a/troubleshoot/monitoring/node-bootlooping.md b/troubleshoot/monitoring/node-bootlooping.md
index 952ac7a46c..79d5f2e31c 100644
--- a/troubleshoot/monitoring/node-bootlooping.md
+++ b/troubleshoot/monitoring/node-bootlooping.md
@@ -39,7 +39,7 @@ Following are some frequent causes of a failed configuration change:
 If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). For an example, see this [video walkthrough](https://www.youtube.com/watch?v=8MnXZ9egBbQ).
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 ## Secure settings [ec-config-change-errors-secure-settings]
diff --git a/troubleshoot/monitoring/performance.md b/troubleshoot/monitoring/performance.md
index 93341acdc5..e7b79b9350 100644
--- a/troubleshoot/monitoring/performance.md
+++ b/troubleshoot/monitoring/performance.md
@@ -20,5 +20,5 @@ Between just after 00:10 and 00:20, excessively high CPU usage consumes all CPU
 If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
diff --git a/troubleshoot/monitoring/unavailable-nodes.md b/troubleshoot/monitoring/unavailable-nodes.md
index aa72aafda4..5c70d10015 100644
--- a/troubleshoot/monitoring/unavailable-nodes.md
+++ b/troubleshoot/monitoring/unavailable-nodes.md
@@ -39,7 +39,7 @@ Some actions described here, such as stopping indexing or Machine Learning jobs,
 For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md).
diff --git a/troubleshoot/monitoring/unavailable-shards.md b/troubleshoot/monitoring/unavailable-shards.md
index 79140904da..c960fd58a9 100644
--- a/troubleshoot/monitoring/unavailable-shards.md
+++ b/troubleshoot/monitoring/unavailable-shards.md
@@ -33,7 +33,7 @@ If a cluster has unassigned shards, you might see an error message such as this
 :::
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md).

From a089c2935a440f7788a08a08cb8275aa83c92b9e Mon Sep 17 00:00:00 2001
From: Marci W <333176+marciw@users.noreply.github.com>
Date: Mon, 24 Mar 2025 11:32:11 -0400
Subject: [PATCH 2/2] gramarrrr

---
 troubleshoot/elasticsearch/increase-shard-limit.md    | 2 +-
 troubleshoot/elasticsearch/rejected-requests.md       | 2 +-
 troubleshoot/monitoring/cluster-response-time.md      | 2 +-
 troubleshoot/monitoring/deployment-health-warnings.md | 2 +-
 troubleshoot/monitoring/high-availability.md          | 2 +-
 troubleshoot/monitoring/high-memory-pressure.md       | 2 +-
 troubleshoot/monitoring/node-bootlooping.md           | 2 +-
 troubleshoot/monitoring/performance.md                | 2 +-
 troubleshoot/monitoring/unavailable-nodes.md          | 2 +-
 troubleshoot/monitoring/unavailable-shards.md         | 2 +-
 10 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md
index 7698c9aa6c..8d9fa04911 100644
--- a/troubleshoot/elasticsearch/increase-shard-limit.md
+++ b/troubleshoot/elasticsearch/increase-shard-limit.md
@@ -128,5 +128,5 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec
 ::::::
 
 :::{tip}}
-If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
diff --git a/troubleshoot/elasticsearch/rejected-requests.md b/troubleshoot/elasticsearch/rejected-requests.md
index fc66ffd964..67a6f8d4a0 100644
--- a/troubleshoot/elasticsearch/rejected-requests.md
+++ b/troubleshoot/elasticsearch/rejected-requests.md
@@ -12,7 +12,7 @@ When {{es}} rejects a request, it stops the operation and returns an error with
 * High [indexing pressure](elasticsearch://reference/elasticsearch/index-settings/pressure.md) that exceeds the [`indexing_pressure.memory.limit`](elasticsearch://reference/elasticsearch/index-settings/pressure.md#memory-limits).
 
 ::::{tip}
-If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 
 ::::
 
diff --git a/troubleshoot/monitoring/cluster-response-time.md b/troubleshoot/monitoring/cluster-response-time.md
index 6faa84dd9a..3e7fab3df8 100644
--- a/troubleshoot/monitoring/cluster-response-time.md
+++ b/troubleshoot/monitoring/cluster-response-time.md
@@ -22,5 +22,5 @@ So what caused the sudden increase in response times? The key to the puzzle lies
 This cluster was sized to handle a certain number of user requests. As the user requests exceeded the maximum throughput that a cluster of this size could sustain, response times increased. To avoid such a slowdown, you either need to control the volume of user requests that reaches the {{es}} cluster or you need to size your cluster to be able to accommodate a sudden increase in user requests.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/deployment-health-warnings.md b/troubleshoot/monitoring/deployment-health-warnings.md
index ae58116616..28281b255a 100644
--- a/troubleshoot/monitoring/deployment-health-warnings.md
+++ b/troubleshoot/monitoring/deployment-health-warnings.md
@@ -29,5 +29,5 @@ If multiple health warnings appear for one of your deployments, or if your deplo
 If the warning refers to a system change, check the deployment’s [Activity](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) page.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/high-availability.md b/troubleshoot/monitoring/high-availability.md
index b8352c46f4..7ada773692 100644
--- a/troubleshoot/monitoring/high-availability.md
+++ b/troubleshoot/monitoring/high-availability.md
@@ -24,5 +24,5 @@ This CPU usage graph indicates that your cluster is load-balancing between the n
 Even if your cluster is performing well, you still need to make sure that there is sufficient spare capacity to deal with the outage of an entire availability zone. For this cluster to remain highly available at all times, you either need to increase its size or reduce its workload.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
\ No newline at end of file
diff --git a/troubleshoot/monitoring/high-memory-pressure.md b/troubleshoot/monitoring/high-memory-pressure.md
index 6f680d1d6b..1cf78e134e 100644
--- a/troubleshoot/monitoring/high-memory-pressure.md
+++ b/troubleshoot/monitoring/high-memory-pressure.md
@@ -30,7 +30,7 @@ In our example, the **Index Response Times** metric shows that high memory press
 If the performance impact from high memory pressure is not acceptable, you need to increase the cluster size or reduce the workload.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 ## Increase the deployment size [ec_increase_the_deployment_size]
diff --git a/troubleshoot/monitoring/node-bootlooping.md b/troubleshoot/monitoring/node-bootlooping.md
index 79d5f2e31c..b14864d665 100644
--- a/troubleshoot/monitoring/node-bootlooping.md
+++ b/troubleshoot/monitoring/node-bootlooping.md
@@ -39,7 +39,7 @@ Following are some frequent causes of a failed configuration change:
 If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). For an example, see this [video walkthrough](https://www.youtube.com/watch?v=8MnXZ9egBbQ).
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 ## Secure settings [ec-config-change-errors-secure-settings]
diff --git a/troubleshoot/monitoring/performance.md b/troubleshoot/monitoring/performance.md
index e7b79b9350..b039265bcf 100644
--- a/troubleshoot/monitoring/performance.md
+++ b/troubleshoot/monitoring/performance.md
@@ -20,5 +20,5 @@ Between just after 00:10 and 00:20, excessively high CPU usage consumes all CPU
 If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
diff --git a/troubleshoot/monitoring/unavailable-nodes.md b/troubleshoot/monitoring/unavailable-nodes.md
index 5c70d10015..277c7ffb29 100644
--- a/troubleshoot/monitoring/unavailable-nodes.md
+++ b/troubleshoot/monitoring/unavailable-nodes.md
@@ -39,7 +39,7 @@ Some actions described here, such as stopping indexing or Machine Learning jobs,
 For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts.
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md).
diff --git a/troubleshoot/monitoring/unavailable-shards.md b/troubleshoot/monitoring/unavailable-shards.md
index c960fd58a9..25f1b750c5 100644
--- a/troubleshoot/monitoring/unavailable-shards.md
+++ b/troubleshoot/monitoring/unavailable-shards.md
@@ -33,7 +33,7 @@ If a cluster has unassigned shards, you might see an error message such as this
 :::
 
 :::{important}
- If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
+ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
 :::
 
 If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md).