Revise issue template (again)

Folks will now know to pastebin their backtraces and M-x doom/info
instead of pasting it in verbatim, right?

...Right?

.github/ISSUE_TEMPLATE/bug_report.md

@@ -17,34 +17,32 @@ about: Doom might be misbehaving
 
 
 **Additional details:**
-- Include a link to your private config
+<!--
+- Link to your private config, if possible
 - Include screenshots/casts of your issue
-- If you mention key sequences, include what commands they're bound to (use `SPC
+- Replace key sequences in your steps to reproduce, use commands
-  h k KEY` or `C-h h k KEY` to inspect keys).
 - Include any warnings or errors logged to \*Messages\* (use `M-x
   view-echo-area-messages` to see it).
-
+- If an error message is involved produce a backtrace of it, copy it to
-<!--
+  pastebin.com, and post the link here.
-  If an error message is involved include a backtrace of it. 
-  
-  Post it on pastebin.com and paste the link here.
 
   How to acquire a backtrace:
 https://doomemacs.org/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error
 -->
 
+
 **Steps to reproduce:**
 1. Select these example steps,
 2. Delete them,
-3. And replace them with precise steps to reproduce your issue.
+3. Replace them with precise steps to reproduce your issue.
-4. Include code samples and keybinds.
+4. Include code samples, keybinds, and commands.
 5. Please don't skimp on details.
-6. Then fill in "system information" below or this issue will be immediately
+6. Then fill in "system information" below or this issue will be deleted.
-   deleted.
 
 
 **System information:**
 <!--
-  Post the output of `M-x doom/info` or `~/.emacs.d/bin/doom info` to
+  1. Grab output from `M-x doom/info` or `~/.emacs.d/bin/doom info`,
-  pastebin.com and paste the link here.
+  2. Paste it into pastebin.com,
-<!--
+  3. Paste URL above this commented block.
+-->