more cleanup

Author: marciw

troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md

@@ -15,23 +15,18 @@ You remove Elastic Cloud Enterprise by removing all containers on the host:
 
 * If using Docker
 
-::::{admonition} 
+
 ```sh
 docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a
 ```
 
-::::
-
 
 * If using Podman
 
-::::{admonition} 
 ```sh
 sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a
 ```
 
-::::
-
 
 If you plan to reinstall Elastic Cloud Enterprise on the host, make sure you [delete the host](../../../deploy-manage/maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old Elastic Cloud Enterprise installation.
 

troubleshoot/elasticsearch/circuit-breaker-errors.md

@@ -11,7 +11,7 @@ By default, the [parent circuit breaker](https://www.elastic.co/guide/en/elastic
 
 See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough of diagnosing circuit breaker errors.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/diagnose-unassigned-shards.md

@@ -233,7 +233,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.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/diagnostic.md

@@ -15,7 +15,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.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::
@@ -69,8 +69,7 @@ To capture an {{es}} diagnostic:
     sudo .\diagnostics.bat --type local --host localhost --port 9200 -u elastic -p --bypassDiagVerify --ssl --noVerify
     ```
 
-    ::::{admonition} Script execution modes
-    :class: tip
+    ::::{tip}
 
     You can execute the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types):
 

troubleshoot/elasticsearch/elasticsearch-reference.md

@@ -8,7 +8,7 @@ mapped_pages:
 
 This section provides a series of troubleshooting solutions aimed at helping users fix problems that an {{es}} deployment might encounter.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/fix-common-cluster-issues.md

@@ -11,7 +11,7 @@ mapped_pages:
 
 This guide describes how to fix common errors and problems with {{es}} clusters.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/fix-watermark-errors.md

@@ -15,7 +15,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](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html#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.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/high-cpu-usage.md

@@ -12,7 +12,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).
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/high-jvm-memory-pressure.md

@@ -7,7 +7,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%.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

troubleshoot/elasticsearch/hotspotting.md

@@ -11,7 +11,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](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html). Temporary spikes are not usually considered problematic, but ongoing significantly unique utilization may lead to cluster bottlenecks and should be reviewed.
 
-::::{admonition}
+::::{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](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::