diff --git a/bukkit/src/main/java/net/william278/husksync/migrator/LegacyMigrator.java b/bukkit/src/main/java/net/william278/husksync/migrator/LegacyMigrator.java
index 5487d6e7..812fea60 100644
--- a/bukkit/src/main/java/net/william278/husksync/migrator/LegacyMigrator.java
+++ b/bukkit/src/main/java/net/william278/husksync/migrator/LegacyMigrator.java
@@ -217,16 +217,16 @@ public class LegacyMigrator extends Migrator {
     @NotNull
     @Override
     public String getName() {
-        return "HuskSync v1.x --> v2.x Migrator";
+        return "HuskSync v1.x --> v3.x Migrator";
     }
 
     @NotNull
     @Override
     public String getHelpMenu() {
         return """
-                === HuskSync v1.x --> v2.x Migration Wizard =========
+                === HuskSync v1.x --> v3.x Migration Wizard =========
                 This will migrate all user data from HuskSync v1.x to
-                HuskSync v2.x's new format. To perform the migration,
+                HuskSync v3.x's new format. To perform the migration,
                 please follow the steps below carefully.
 
                 [!] Existing data in the database will be wiped. [!]
diff --git a/common/src/main/java/net/william278/husksync/config/Locales.java b/common/src/main/java/net/william278/husksync/config/Locales.java
index d72d8653..f59d105c 100644
--- a/common/src/main/java/net/william278/husksync/config/Locales.java
+++ b/common/src/main/java/net/william278/husksync/config/Locales.java
@@ -40,7 +40,7 @@ import java.util.Optional;
         ┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
         ┣╸ See plugin about menu for international locale credits
         ┣╸ Formatted in MineDown: https://github.com/Phoenix616/MineDown
-        ┗╸ Translate HuskSync: https://william278.net/docs/husksync/Translations""")
+        ┗╸ Translate HuskSync: https://william278.net/docs/husksync/translations""")
 public class Locales {
 
     /**
diff --git a/docs/Legacy-Migration.md b/docs/Legacy-Migration.md
index 46284065..483ec681 100644
--- a/docs/Legacy-Migration.md
+++ b/docs/Legacy-Migration.md
@@ -1,4 +1,4 @@
-This guide will walk you through how to upgrade from HuskSync v1.4.x to HuskSync v2.x or v3.x. Data from HuskSync v2.x will automatically be imported into HuskSync v3.x.
+This guide will walk you through how to upgrade from HuskSync v1.4.x to HuskSync v3.x. Data from HuskSync v2.x will automatically be imported into HuskSync v3.x.
 
 ## Requirements
 - MySQL Database with HuskSync v1.4.x data
@@ -9,15 +9,15 @@ This guide will walk you through how to upgrade from HuskSync v1.4.x to HuskSync
 ### 1. Uninstall HuskSync v1.x from all servers
 - Switch off all servers and your proxy
 - Delete the .jar file from your `~/plugins/` folders on your Spigot servers
-- Also delete the .jar file from your `~/plugins/` folders on your Proxy. HuskSync v2.x no longer requires a proxy plugin.
-- Delete (or make a copy and delete) all HuskSync config data folders (`~/plugins/HuskSync/`). HuskSync 2.x has a new config and messages file.
+- Also delete the .jar file from your `~/plugins/` folders on your Proxy. HuskSync v3.x no longer requires a proxy plugin.
+- Delete (or make a copy and delete) all HuskSync config data folders (`~/plugins/HuskSync/`). HuskSync v3.x has new `config.yml`, `messages-xx-xx.yml` and `server.yml` files.
 
-### 2. Install HuskSync v2.x on all Spigot servers
-- HuskSync v2.x must only be installed on your Spigot servers, not your proxy.
+### 2. Install HuskSync v3.x on all Spigot servers
+- HuskSync v3.x must only be installed on your Spigot servers, not your proxy.
 - Follow the setup instructions [here](Setup).
 
 ### 3. Configure the migrator
-- With your servers back on and correctly configured to run HuskSync v2.x, ensure nobody is online.
+- With your servers back on and correctly configured to run HuskSync v3.x, ensure nobody is online.
 - Use the console on one of your Spigot servers to enter: `husksync migrate legacy`
 - Carefully read the migration configuration instructions. In most cases, you won't have to change the settings, but if you do need to adjust them, use `husksync migrate legacy set <setting> <value>`.
 - Migration will be carried out *from* the database you specify with the settings in console *to* the database configured in `config.yml`. If you're migrating from multiple clusters, ensure you run the migrator on the correct servers corresponding to the migrator.