update macos log

Author: caesay

docs/troubleshooting/debugging.mdx

@@ -30,9 +30,12 @@ new UpdateManager("https://path.to/your-updates", logger: new ConsoleLogger());
 ### Windows
 Running Update.exe will log most output to it's base directory as `Velopack.log`. Setup.exe will not log to file by default. However, you can override the log location for both binaries with the `--log {path}` parameter. You can also use the `--verbose` flag to capture debug/trace output to log. Unfortunately, on Windows, to avoid showing up as a console window, these binaries are compiled as a WinExe and there will be no console output by default.  Please see the [command line reference](cli.mdx) for a comprehensive list of arguments supported.
 
-### MacOS / Linux
+### Linux
 All logs will be sent to `/tmp/velopack.log`.
 
+### MacOS
+Logs will be sent to `/tmp/velopack.log` or `~Library/Logs/velopack.log` depending on your version of Velopack.
+
 ## Advanced Debugging
 The debug builds of Velopack binaries have additional logging/debugging capabilities, and will produce console output. In some instances, it may be useful to [compile Velopack](../contributing/compiling.mdx) for your platform, and replace the release binaries of Setup.exe and Update.exe with debug versions.