Update getting-help.md

docs/en/manuals/getting-help.md

@@ -28,12 +28,25 @@ A good way to discuss and get help with a problem is to post a question on our [
   - OS: [e.g. iOS8.1, Windows 10, High Sierra]
   - Device: [e.g. iPhone6]
 
-* **Logs (OPTIONAL)** - Please include any relevant logs. This can be device logs or editor logs. Editor logs are located here:
-  - Windows: C:\Users\ **Your Username** \AppData\Local\Defold
-  - macOS: /Users/ **Your Username** /Library/Application Support/ or ~/Library/Application Support/Defold
-  - Linux: ~/.Defold
+* **Logs (OPTIONAL)** - Please include any relevant logs (engine and/or editor). Editor logs are located here:
+  - Windows: `C:\Users\ **Your Username** \AppData\Local\Defold`
+  - macOS: `/Users/ **Your Username** /Library/Application Support/` or `~/Library/Application Support/Defold`
+  - Linux: `~/.Defold`
 
-* **Minimal repro case project (OPTIONAL)** - Please attach a minimal project where the bug is reproduced. This will greatly help the person trying to investigate and fix the bug.
+  Engine logs for Android can be accessed using the `adb` command line tool (Android Debug Bridge). Read more about the `adb` command line tool in the [Android manual](/manuals/android/#_android_debug_bridge).
+
+  Engine logs for iOS can be accessed using XCode and the Devices and Simulators menu option.
+
+  Engine logs for HTML5 builds can be viewed in the browser developer console:
+  - Chrome: Menu > More Tools > Developer Tools
+  - Firefox: Tools > Web Developer > Web Console
+  - Safari: Develop > Show JavaScript Console
+
+  Engine logs for desktop builds can be viewed by running the Defold application from a terminal/command prompt.
+
+  You can also write engine logs to a file and access this once the application has been shut down. You can read more about how to enable and access the log in the [Debugging manual](/manuals/debugging/#_extracting_the_log.txt_file).uild
+
+* **Minimal repro case project (OPTIONAL)** - Please attach a minimal project where the bug is reproduced. This will greatly help the person trying to investigate and fix the bug. If you share the project as a zip file make sure to exclude the `.git`, `.internal` and `build` folders from the archive.
 
 * **Workaround (OPTIONAL)** - If there is a workaround, please describe it here.