diff --git a/_docs/master/developers-guide/community-drivers.md b/_docs/master/developers-guide/community-drivers.md
index 2b13b29798..dd6d719aba 100644
--- a/_docs/master/developers-guide/community-drivers.md
+++ b/_docs/master/developers-guide/community-drivers.md
@@ -14,6 +14,7 @@ redirect_from:
 
 # Community drivers
 
+> [!NOTE]
 > Community drivers are not supported on [Metabase Cloud](/cloud/).
 
 In addition to our [Officially supported drivers](../databases/connecting#connecting-to-supported-databases), many people build and maintain drivers for database integrations.
@@ -29,6 +30,7 @@ You can change the location of the plugins directory by setting the environment
 
 ## Community drivers
 
+> [!WARNING]
 > You install these drivers at your own risk. The plugins run as part of your Metabase and will have access to anything your Metabase does. And since we can’t vet for them, we don’t make them available on [Metabase Cloud](/cloud/).
 
 Anyone can build a community driver. These are the currently known third-party database drivers for Metabase.
diff --git a/_docs/master/installation-and-operation/upgrading-metabase.md b/_docs/master/installation-and-operation/upgrading-metabase.md
index 805935487d..f33cb7c616 100644
--- a/_docs/master/installation-and-operation/upgrading-metabase.md
+++ b/_docs/master/installation-and-operation/upgrading-metabase.md
@@ -147,6 +147,8 @@ Durning a **minor version upgrade** (e.g., 54.1 to 54.2), the new Metabase conta
 
 ## Rolling back an upgrade or to an older version
 
+> **The downgrade command must be run on the JAR with the higher version number.**
+
 In general, regular backups (especially backups before upgrading), are the best policy, so we recommend reverting to a backup of your application database to roll back an upgrade.
 
 But if you've made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the `migrate down` command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The `migrate down` command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you definitely remembered to generate before upgrading), and only using the `migrate down` command if you really need to keep changes made after your upgrade.
diff --git a/_site/docs/master/developers-guide/community-drivers.html b/_site/docs/master/developers-guide/community-drivers.html
index 18e0f82d2e..8ab9c35feb 100644
--- a/_site/docs/master/developers-guide/community-drivers.html
+++ b/_site/docs/master/developers-guide/community-drivers.html
@@ -49,7 +49,7 @@
 <meta name="twitter:site" content="@metabase">
 
 <meta name="twitter:title" content="Community drivers | Metabase Documentation">
-<meta name="twitter:description" content="Community drivers  Community drivers are not supported on Metabase Cloud.  In addition to our Officially supported drivers, many people build and maintain drivers for database integrations. How to use a Community driver To use a Community...">
+<meta name="twitter:description" content="Community drivers  [!NOTE] Community drivers are not supported on Metabase Cloud.  In addition to our Officially supported drivers, many people build and maintain drivers for database integrations. How to use a Community driver To use a...">
 <meta name="twitter:card" content="summary_large_image">
 <meta name="twitter:image" content="https://www.metabase.com/images/docs/docs-og.png">
 <!-- end of Twitter cards -->
@@ -59,7 +59,7 @@
 <meta property="og:type" content="article">
 <meta property="og:url" content="https://www.metabase.com/docs/master/developers-guide/community-drivers">
 <meta name="title" property="og:title" content="Community drivers | Metabase Documentation">
-<meta name="description" property="og:description" content="Community drivers  Community drivers are not supported on Metabase Cloud.  In addition to our Officially supported drivers, many people build and maintain drivers for database integrations. How to use a Community driver To use a Community...">
+<meta name="description" property="og:description" content="Community drivers  [!NOTE] Community drivers are not supported on Metabase Cloud.  In addition to our Officially supported drivers, many people build and maintain drivers for database integrations. How to use a Community driver To use a...">
 <meta name="image" property="og:image" content="https://www.metabase.com/images/docs/docs-og.png">
 <!-- end of Open Graph metadata -->
 
@@ -4727,7 +4727,8 @@ <h5>Other resources</h5>
         <h1 id="community-drivers">Community drivers</h1>
 
 <blockquote>
-  <p>Community drivers are not supported on <a href="/cloud/">Metabase Cloud</a>.</p>
+  <p>[!NOTE]
+Community drivers are not supported on <a href="/cloud/">Metabase Cloud</a>.</p>
 </blockquote>
 
 <p>In addition to our <a href="../databases/connecting#connecting-to-supported-databases">Officially supported drivers</a>, many people build and maintain drivers for database integrations.</p>
@@ -4746,7 +4747,8 @@ <h2 id="how-to-use-a-community-driver">How to use a Community driver</h2>
 <h2 id="community-drivers-1">Community drivers</h2>
 
 <blockquote>
-  <p>You install these drivers at your own risk. The plugins run as part of your Metabase and will have access to anything your Metabase does. And since we can’t vet for them, we don’t make them available on <a href="/cloud/">Metabase Cloud</a>.</p>
+  <p>[!WARNING]
+You install these drivers at your own risk. The plugins run as part of your Metabase and will have access to anything your Metabase does. And since we can’t vet for them, we don’t make them available on <a href="/cloud/">Metabase Cloud</a>.</p>
 </blockquote>
 
 <p>Anyone can build a community driver. These are the currently known third-party database drivers for Metabase.</p>
diff --git a/_site/docs/master/installation-and-operation/upgrading-metabase.html b/_site/docs/master/installation-and-operation/upgrading-metabase.html
index d1ea915ef5..ab99ce805a 100644
--- a/_site/docs/master/installation-and-operation/upgrading-metabase.html
+++ b/_site/docs/master/installation-and-operation/upgrading-metabase.html
@@ -4881,6 +4881,10 @@ <h2 id="what-happens-during-an-upgrade-or-downgrade">What happens during an upgr
 
 <h2 id="rolling-back-an-upgrade-or-to-an-older-version">Rolling back an upgrade or to an older version</h2>
 
+<blockquote>
+  <p><strong>The downgrade command must be run on the JAR with the higher version number.</strong></p>
+</blockquote>
+
 <p>In general, regular backups (especially backups before upgrading), are the best policy, so we recommend reverting to a backup of your application database to roll back an upgrade.</p>
 
 <p>But if you’ve made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the <code class="language-plaintext highlighter-rouge">migrate down</code> command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The <code class="language-plaintext highlighter-rouge">migrate down</code> command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you definitely remembered to generate before upgrading), and only using the <code class="language-plaintext highlighter-rouge">migrate down</code> command if you really need to keep changes made after your upgrade.</p>