Docs: Clarify Auto Tools Usage Note
@@ -596,21 +596,18 @@ the \hyperref[miscsecurityprops]{Security Properties} section of this document.
The \texttt{OC\ config} file, as with any property list file, can be edited with
any text editor, such as nano or vim. However, specialised software
may provide a better experience. On macOS, the preferred GUI application is
-\href{https://developer.apple.com/xcode}{Xcode}. For a lightweight
-cross-platform and open-source alternative, the
-\href{https://github.com/corpnewt/ProperTree}{ProperTree} editor can be
-utilised.
-
-It is strongly advised not to use any software that is aware of the internal
-configration structure as it constantly gets out of date and will cause
-incorrect configuration to be generated. If it is a must desprite the
-warning one should make sure to only use stable versions of OpenCore
-with explicit support for the particular version in the app. The choice
-of open-source implementations with transparent binary generation
-is encouraged (e.g. \href{https://github.com/ic005k/QtOpenCoreConfig}{OCAT}),
-since other tools may contain malware. Remember that a configuration
-made for a different hardware setup shall never be used on another hardware
-setup.
+\href{https://developer.apple.com/xcode}{Xcode}. The
+\href{https://github.com/corpnewt/ProperTree}{ProperTree} editor
+is a lightweight, cross-platform and open-source alternative.
+
+It is strongly recommended to avoid configuration creation tools that are aware of the
+internal configuration structure as this may result in invalid configurations (since the
+structure gets constantly updated). If such tools are to be used despite this warning,
+ensure that only stable versions of OpenCore explicitly supported by such tools are used.
+In such cases, the use of open-source implementations with transparent binary generation
+(such as \href{https://github.com/ic005k/QtOpenCoreConfig}{OCAT}) is encouraged, given
+that other tools may contain malware. In addition, configurations created for a specific
+hardware setup should never be used on different hardware setups.
For BIOS booting, a third-party UEFI environment provider is required and
\texttt{OpenDuetPkg} is one such UEFI environment provider for legacy systems.
