-If available, please a backtrace of the error here.
+Include a backtrace of the error.
-To acquire a backtrace, enable `debug-on-error` then recreate the error. Here
-are ways to enable `debug-on-error`:
-- `M-x toggle-debug-on-error`,
-- Start Emacs with `emacs --debug-init`
-- If the error occurred while using `bin/doom`, use the `-d`/`--debug`
-- switches or the `DEBUG` environment variable.
+How to acquire a backtrace:
+https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index b3b4514c6..7148f9f30 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,22 +1,19 @@
---
name: Feature request
-about: Make suggestions for improving Doom Emacs
+about: It'd be cool if Doom did/had/would...
labels: is:request
title: "[REQUEST] "
assignees: ''
---
**Describe the feature**
-Start with a brief 1 or 2 sentence summary of feature.
-
-Then follow up with an extended explanation, if necessary. Here are some
-suggestions on what to include:
+- What is your request?
- How is it helpful?
-- How is the feature used?
+- How is it used?
- If the feature involves new plugins, include links to them
-- iF the feature involves replacement of current functionality, describe how the
- new functionality is better.
-- If the feature is implemented in another editor Emacs distro:
+- If the feature involves replacement of current functionality, how the new
+ functionality is better?
+- If the feature is implemented in another editor or Emacs distro:
- Include screenshots or screencasts of it
- Include links to its implementation
- Include names of commands (and not just the keybinds to invoke them)
@@ -25,4 +22,7 @@ suggestions on what to include:
**System information**