Improve what to do if something fails section

pages/merlin7/99-support/migration-from-merlin6.md

@@ -140,17 +140,25 @@ This script will:
 * Automatically track the job IDs
 * Print log file locations for the different jobs
 
-If something goes wrong:
-* Users have to check the reason in the job logs and fix it.
-* Please read [⚠️ Common rsync/fpsync Migration Issues](/merlin7/migrating.html#%EF%B8%8F--common-rsyncfpsync-migration-issues)
-  to see how to solve some of the commonest problems.
-* If `migrate_merlin6data.batch` fails, `migrate_merlin6home.batch` will be cancelled.
-* **Once the issues are fixed, users should restart the migration with `merlin7_migration.start`**
-  * Migration will continue.
-
 > ⚠️ **Once both transfers succeed, your access to Merlin6 will be revoked.**
 > Do **not** attempt to reconnect to Merlin6 after this.
 
+### ❗ If Something Goes Wrong
+
+If a problem occurs during the migration process:
+
+* 🔍 **Check the job log files** mentioned in the script output. They contain detailed messages that explain what failed and why.
+* 🛠️ **Fix the root cause** on the source system. Common issues include:
+
+  * Files with incorrect permissions
+  * Ownership mismatches
+  * Disk quota exceeded on Merlin7
+* 📚 Refer to the [⚠️ Common rsync/fpsync Migration Issues](/merlin7/migrating.html#%EF%B8%8F--common-rsyncfpsync-migration-issues) section below for detailed explanations and solutions.
+
+> ℹ️ **Important:** If `migrate_merlin6data.batch` fails, the migration process will automatically cancel `migrate_merlin6home.batch` to avoid ending in an inconsistent state.
+
+Once the problem is resolved, simply re-run the `merlin7_migration.start` script to resume the migration.
+
 ---
 
 ## 📊 Step 3: Monitor Transfer Jobs