Iter

Author: DaveCTurner

deploy-manage/upgrade/prepare-to-upgrade.md

@@ -56,20 +56,15 @@ Review the following best practices to upgrade your deployments.
 
 1. Before upgrading your production deployment, test the upgrade using an isolated environment. Ensure the test and production environments use the same settings.
 
-    :::{important}
     The upgraded version of {{es}} may interact with its environment in different ways from the version you are currently running. It is possible that your environment behaves incorrectly in a way that does not matter to the version of {{es}} that you are currently running, but which does matter to the upgraded version. In this case, the upgraded version will not work correctly until you address the incorrect behaviour in your environment.
 
     During your upgrade tests, pay particular attention to the following aspects:
 
-    Cluster stability
-    : Does the new version of {{es}} form a stable healthy cluster?
+    *Cluster stability*: Does the new version of {{es}} form a stable healthy cluster?
 
-    Indexing and search performance
-    : Does the new version of {{es}} perform the same (or better) than the current one on your specific workload and data?
+    *Indexing and search performance*: Does the new version of {{es}} perform the same (or better) than the current one on your specific workload and data?
 
-    Snapshots
-    : Do all of your snapshot repositories work correctly and pass [repository analysis](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze)?
-    :::
+    *Snapshots*: Do all of your snapshot repositories work correctly and pass [repository analysis](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze)?
 
 1. Create a snapshot of your production deployment before starting the upgrade.