From 95d322b427aa930d527cf74d40d2b37c96b3539dfde2da9b96966d070d577c09 Mon Sep 17 00:00:00 2001
From: anonoe <8bdd1ef7-1633-4e26-83a0-8dda8605bcd0@aleeas.com>
Date: Sun, 20 Apr 2025 20:54:42 +0200
Subject: [PATCH] Update WIP Updating MMS-client from 1.2 to 3.0

---
 WIP Updating MMS-client from 1.2 to 3.0.-.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

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 e325582..05b29e3 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	
@@ -1,7 +1,7 @@
 Updating MMS-client from 1.2.x to 3.0 requires manual intervention, if you do not want to install 3.0 to a new, separate instance.
 ### Update Methods
 
-1. Install 3.0 to a new, separate instance.
+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 configurations/settings, DistantHorizons LODs, logs, your Xaero world map  
@@ -16,4 +16,11 @@ This is because no data is transferred from your 1.2 installation. You start wit
 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
+- Cons: You will install with quite a hassle and can start playing with 3.0 only after some time.
+
+
+### Install 3.0 to a new, separate instance
+
+### (Best trade-off) Quickly migrate data from your 1.2 installation
+
+### Migrate all data from your 1.2 installation
\ No newline at end of file