diff --git a/WIP Updating MMS-client from 1.2 to 3.0.-.md b/WIP Updating MMS-client from 1.2 to 3.0.-.md
index 639db80..e99da3b 100644
--- a/WIP Updating MMS-client from 1.2 to 3.0.-.md	
+++ b/WIP Updating MMS-client from 1.2 to 3.0.-.md	
@@ -4,10 +4,16 @@ Updating MMS-client from 1.2.x to 3.0 requires manual intervention, if you do no
 1. Install 3.0 to a new, separate instance.
 
 - Pros: You can install it without hassle and start playing with 3.0 in no time.
-- Cons: You might miss some things, like your configuration, DistantHorizons LODs, logs, your Xaero world map  
- mods and resourcepacks if you added any, 
+- Cons: You might miss some things, like your configurations/settings, DistantHorizons LODs, logs, your Xaero world map  
+and if you added any of the following: mods, resourcepacks, singleplayer worlds, servers...  
+This is because no data is transferred from your 1.2 installation. You start with a fresh new 3.0 installation.
 
-2. ass
+2. Quickly migrate data from your 1.2 installation
 
+- Pros: You can install with little hassle and start playing with 3.0 in almost no time
+- Cons: You might miss your configurations/settings and if you added any mods or resourcepacks if you edited 'fancy', '3D' or 'utility' via VTDownloader  
 
-DH_server_data folder must be renamed to match new server name (nanoMMS -> MMS)
\ No newline at end of file
+3. Migrate all data from your 1.2 installation
+
+- Pros: You keep all your data
+- Cons: You will install with quite a hassle and can start playing with 3.0 only after some time.
\ No newline at end of file