diff --git a/content/docs/blueprint/migrations/docker.mdx b/content/docs/blueprint/migrations/docker.mdx
index 66dc6f1..b1f990c 100644
--- a/content/docs/blueprint/migrations/docker.mdx
+++ b/content/docs/blueprint/migrations/docker.mdx
@@ -7,7 +7,7 @@ description: Guide for migrating from Pyrodactyl to Pyrodactyl (Blueprint) using
 <Callout type='warning'>
 Always ensure that you make a backup of your Pyrodactyl database and any other relevant data. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use)
 
-```
+```bash
 # If using MySQL
 mysqldump -u root -p --opt panel > ./panel.sql
 
@@ -19,12 +19,12 @@ mariadb-dump -u root -p --opt panel > ./panel.sql
 If you already have Pyrodactyl running in Docker, update your panel image and add these volumes to your `docker-compose.yml` file:
 ```diff
 panel:
-   -image: ghcr.io/pyrohost/pyrodactyl:main
-   +image: ghcr.io/pyrodactyl-oss/blueprint:latest
+-  image: ghcr.io/pyrohost/pyrodactyl:main
++  image: ghcr.io/pyrodactyl-oss/blueprint:latest
 
 volumes:
-    + - "/srv/pyrodactyl/extensions/:/blueprint_extensions"
-    + - "app:/app"
++  - "/srv/pyrodactyl/extensions/:/blueprint_extensions"
++  - "app:/app"
 ```
 
 <Callout type='error'>
diff --git a/content/docs/pyrodactyl/migrations/docker.mdx b/content/docs/pyrodactyl/migrations/docker.mdx
index 9624e22..c72b95d 100644
--- a/content/docs/pyrodactyl/migrations/docker.mdx
+++ b/content/docs/pyrodactyl/migrations/docker.mdx
@@ -9,8 +9,16 @@ description: Guide for migrating from Pterodactyl to Pyrodactyl using Docker
 
 ## Migrating from Pterodactyl (Docker)
 
-<Callout type="warn">
-  Always make sure you take a backup of your Pterodactyl database and other relevant data.
+<Callout type='error'>
+Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use)
+
+```bash
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
 </Callout>
 
 If you already have Pterodactyl running in Docker, simply update your panel image in your `docker-compose.yml` file:
diff --git a/content/docs/pyrodactyl/migrations/native-to-docker.mdx b/content/docs/pyrodactyl/migrations/native-to-docker.mdx
index 1a70275..d572365 100644
--- a/content/docs/pyrodactyl/migrations/native-to-docker.mdx
+++ b/content/docs/pyrodactyl/migrations/native-to-docker.mdx
@@ -8,7 +8,7 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac
 <Callout type='error'>
 Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use)
 
-```
+```bash
 # If using MySQL
 mysqldump -u root -p --opt panel > ./panel.sql
 
@@ -26,18 +26,6 @@ mariadb-dump -u root -p --opt panel > ./panel.sql
 - Avoid using Snap-based Docker installations on Ubuntu
 - Enable Docker auto-start on boot
 
-<Callout type='error'>
-Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use)
-
-```
-# If using MySQL
-mysqldump -u root -p --opt panel > ./panel.sql
-
-# If using MariaDB
-mariadb-dump -u root -p --opt panel > ./panel.sql
-```
-</Callout>
-
 ### Pyrodactyl Installation
 
 1. Create a new folder (e.g. `pyrodactyl-panel`) on your server in a safe location, and switch to it.
@@ -82,4 +70,4 @@ mariadb-dump -u root -p --opt panel > ./panel.sql
    docker compose up -d
    ```
 
-Your panel is now running! You can access it at the same URL as before, and use the same user accounts.
\ No newline at end of file
+Your panel is now running! You can access it at the same URL as before, and use the same user accounts.
diff --git a/content/docs/pyrodactyl/migrations/native-to-native.mdx b/content/docs/pyrodactyl/migrations/native-to-native.mdx
index 621eba6..81fff4d 100644
--- a/content/docs/pyrodactyl/migrations/native-to-native.mdx
+++ b/content/docs/pyrodactyl/migrations/native-to-native.mdx
@@ -8,7 +8,7 @@ description: Guide for migrating from native Pterodactyl installation to native
 <Callout type='error'>
 Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. It is also recommended that you make a backup of the Pterodactyl folder aswell if anything goes wrong during migration. (Replace ``panel`` with the database name you use)
 
-```
+```bash
 # If using MySQL
 mysqldump -u root -p --opt panel > ./panel.sql
 
diff --git a/content/docs/pyrodactyl/migrations/native-update.mdx b/content/docs/pyrodactyl/migrations/native-update.mdx
index 4442335..f2ed53b 100644
--- a/content/docs/pyrodactyl/migrations/native-update.mdx
+++ b/content/docs/pyrodactyl/migrations/native-update.mdx
@@ -12,7 +12,7 @@ Newest release version:
 <Callout type="warn">
   Before proceeding with any updates, make sure to back up your database and panel files. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use)
 
-```
+```bash
 # If using MySQL
 mysqldump -u root -p --opt panel > ./panel.sql