Updating troubleshoot page

Author: infeo

docs/desktop/troubleshooting.md

@@ -10,30 +10,35 @@ This page contains solutions for common issues you might encounter when using Cr
 
 ## Log File Locations {#log-file-locations}
 
-Cryptomator creates log files to help with troubleshooting when issues occur. The default locations for these log files vary by operating system:
+Cryptomator creates log files to help with troubleshooting when issues occur.
+The default locations for these log files vary by operating system:
 
 | Operating System | Default Log File Location                    |
 | :--------------- | :------------------------------------------- |
-| Windows          | `%appdata%\Cryptomator\cryptomator.log`      |
-| macOS            | `~/Library/Logs/Cryptomator/cryptomator.log` |
-| Linux            | `~/.Cryptomator/cryptomator.log`             |
+| Windows          | `%localappdata%\Cryptomator\`                |
+| macOS            | `~/Library/Logs/Cryptomator/`                |
+| Linux            | `~/.local/share/Cryptomator/logs/`           |
+
+The log files are named with the pattern `cryptomatorX.log`, where `X` is a number from 0 to 9.
+The most recent log file is always `cryptomator0.log`.
 
-You can change the log file directory by setting the `cryptomator.logDir` property in the [advanced configuration](advanced-settings.md). This allows you to store log files in a custom location if needed.
 
 ## Debug Mode {#debug-mode}
 
 Debug mode enables additional diagnostic logging to help troubleshoot issues with Cryptomator. When debug mode is active, the application records more detailed information about its operations in the log files.
 
 :::warning Privacy Consideration
-With debug mode enabled, the paths of all files you encrypt are stored in the log file. This creates a record of your file and folder names, which may compromise privacy. Only enable debug mode when actively troubleshooting an issue, and remember to disable it afterward.
+With debug mode enabled, _every accessed file and listed directory inside the vault is written in clear text to the log file_. This creates a record of your file and folder names, which may compromise privacy. Only enable debug mode when actively troubleshooting an issue, and remember to disable it afterward.
 :::
 
 To enable debug mode:
 
-1. Open Cryptomator and navigate to the settings
-2. Look for the `Enable debug logging` checkbox and enable it
+1. Open Cryptomator and open the preferences.
+2. In the general tab, look for the `Enable debug logging` checkbox at the bottom and enable it.
 
-The additional debug information will now be written to your log files. Once you have reproduced the issue you're investigating, disable debug mode by unchecking the option to return to normal logging levels.
+Cryptomator will now run in debug mode. The app indicates this by showing a red bar at the bottom of the main window.
+The additional debug information is written to your log files.
+Once you have reproduced the issue you're investigating, disable debug mode by unchecking the option to return to normal logging levels.
 
 ## Known Issues {#known-issues}