more

Author: shainaraskas

deploy-manage/monitor/cloud-health-perf.md

@@ -55,7 +55,7 @@ In the normal course of using your {{ech}} and {{ece}} deployments, health warni
 | --- | --- |
 | Health warning messages | Health warning messages will sometimes appear on the main page for one of your deployments, as well as on the **Logs and metrics** page.<br><br>For {{ech}} deployments, these messages might reflect routine maintenance activity occurring on {{ecloud}}.|
 | Configuration change failures | In more serious cases, your deployment may be unable to restart. The failure can be due to a variety of causes, the most frequent of these being invalid secure settings, expired plugins or bundles, or out of memory errors. The problem is often not detected until an attempt is made to restart the deployment following a routine configuration change, such as a deployment resizing. |
-| Out of memory errors | Out of memory errors (OOMs) may occur during your deployment’s normal operations, and these can have a very negative impact on performance. Common causes of memory shortages are oversharding, data retention oversights, and the overall request volume.<br><br>On your deployment page, you can check the [JVM memory pressure indicator](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md#ec-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, refer to [](/troubleshoot/monitoring/high-memory-pressure.md). |
+| Out of memory errors | Out of memory errors (OOMs) may occur during your deployment’s normal operations, and these can have a very negative impact on performance. Common causes of memory shortages are oversharding, data retention oversights, and the overall request volume.<br><br>On your deployment page, you can check the [JVM memory pressure indicator](/deploy-manage/monitor/ec-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](/deploy-manage/monitor/ec-memory-pressure.md#ec-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, refer to [](/troubleshoot/monitoring/high-memory-pressure.md). |
 
 #### Cluster restarts after out-of-memory failures [ec_cluster_restarts_after_out_of_memory_failures]
 ```{applies_to}

raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md

@@ -59,7 +59,7 @@ To learn more about what [Elasticsearch monitoring metrics](/deploy-manage/monit
 :alt: Node tab in Kibana under Stack Monitoring
 :::
 
-Some [performance metrics](../../../deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
+Some [performance metrics](../../../deploy-manage/monitor/ec-saas-metrics-accessing.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
 
 :::{image} ../../../images/cloud-ec-ce-monitoring-performance.png
 :alt: Performance page of the Elastic Cloud console