Update Troubleshooting section

- Improve instructions for enabling debug logs
- Mention that stdout is not used for logging
- Remove HOMEBREW_PREFIX from logs locations since homebrew installation
  is not recommended.
- Move note about old logs location to a separate note.

Fixes: lima-vm#70
Signed-off-by: Nir Soffer <[email protected]>

README.md

@@ -344,6 +344,10 @@ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/libexec/bootpd
 - [`file:///Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/vmnet.framework/Versions/Current/Headers/vmnet.h`](file:///Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/vmnet.framework/Versions/Current/Headers/vmnet.h)
 
 ## Troubleshooting
-- Set environment variable `DEBUG=1`
-- See `${HOMEBREW_PREFIX}/var/log/socket_vmnet/{stdout,stderr}` (when using launchd).
-  The path was previously `${HOMEBREW_PREFIX}/var/run/socket_vmnet.{stdout,stderr}` until March 2023.
+
+- To enable verbose debug logs, set the environment variable `DEBUG=1`.
+- When using launchd, logs are written to `/var/log/socket_vmnet/stderr`.
+  `/var/log/socket_vmnet/stdout` is not used and expected to be empty.
+
+> [!NOTE]
+> Until March 2023, logs were written to `/var/run/socket_vmnet.{stdout,stderr}`.