Update bug_report.md

update the strace commands and make clear to use a recent release

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,9 +8,14 @@ assignees: ''
 ---
 
 **Describe the bug**
-A clear and concise description of what the bug is. Please do not file bugs for unreleased versions unless you're a tester or sure it's not a work in progress. The master branch is **not** to be considered in a production state.
+
+A clear and concise description of what the bug is. Make sure you've upgraded to the latest release to ensure the issue still exists.
+
+The master branch is **not** to be considered production ready. Feel free to file bug reports but do so indicating clearly that you are testing unreleased code.
+
 
 **To Reproduce**
+
 Steps to reproduce the behavior. List **all** steps to reproduce. **All** settings.
 
 Please simplify the reproduction as much as possible. 
@@ -19,16 +24,24 @@ Please simplify the reproduction as much as possible.
 
 
 **Expected behavior**
+
 A clear and concise description of what you expected to happen.
 
 
 **System information:**
+
  - OS, kernel version: `uname -a`
  - mergerfs version: `mergerfs -V`
  - mergerfs settings
- - List of drives, filesystems, & sizes: `df -h`
- - A strace of the application having a problem: `strace -f -o /tmp/app.strace.txt <cmd>` or `strace -f -p <appPID> -o /tmp/app.strace.txt`
- - strace of mergerfs while app tried to do it's thing: `strace -f -p <mergerfsPID> -o /tmp/mergerfs.strace.txt`
+ - List of drives, filesystems, & sizes:
+   - `df -h`
+   - `lsblk`
+ - A strace of the application having a problem: 
+   - `strace -fvTtt -s 256 -o /tmp/app.strace.txt <cmd>`
+   - `strace -fvTtt -s 256 -o /tmp/app.strace.txt -p <appPID>`
+ - strace of mergerfs while app tried to do it's thing:
+   - `strace -fvTtt -s 256 -p <mergerfsPID> -o /tmp/mergerfs.strace.txt`
 
 **Additional context**
+
 Add any other context about the problem here.