From dde558a9513ac453bb60f6cfb065c9fb86f7ab52 Mon Sep 17 00:00:00 2001
From: neon ball <35791009+ParaDoX1994@users.noreply.github.com>
Date: Tue, 24 Sep 2024 23:02:59 +0300
Subject: [PATCH] Update TROUBLESHOOTING.md

---
 docs/TROUBLESHOOTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/TROUBLESHOOTING.md b/docs/TROUBLESHOOTING.md
index 9cf3a52b3..436aa5eb6 100644
--- a/docs/TROUBLESHOOTING.md
+++ b/docs/TROUBLESHOOTING.md
@@ -81,11 +81,11 @@ With OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure OS updates
 
 ## System version mismatch error when root patching
 
-Updates from now on modify the system volume already while downloading, which can lead to broken patches out of a sudden as well as a "version mismatch" error while root patching as the operating system gets into a liminal state between two versions. 
+Updates from now on modify the system volume already while downloading, which can lead to broken patches out of a sudden as well as a "version mismatch" error while root patching, since the operating system gets into a liminal state between two versions. The "version mismatch" error is a safeguard preventing OCLP from patching on a system that is in an weird liminal state, to avoid leading to a very likely boot failure.
 
 Currently there is a "PurgePendingUpdate" tool available [on the Discord server](https://discord.com/channels/417165963327176704/1037474131526029362/1255993208966742108) you can download and then run it in Terminal, to get rid of a pending update. This may be integrated into OCLP later on, however there is currently no ETA.
 
-You can still manually initiate an update when you're ready to do so.
+Disabling automatic macOS updates is extremely recommended once recovered, to prevent it from happening again.
 
 ## Stuck on boot after root patching