From 09b6804e710f48d8a6a35e15fff7757356bd422a Mon Sep 17 00:00:00 2001
From: baldurk <baldurk@baldurk.org>
Date: Mon, 6 Jan 2020 13:42:46 +0000
Subject: [PATCH] Tweak issue template for clarity

* Make it clear that it's expected for feature requests as well as bug reports.
* Clarify that the API is the graphics API in use.
---
 docs/issue_template.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/issue_template.md b/docs/issue_template.md
index e0fd08c27..d684160b7 100644
--- a/docs/issue_template.md
+++ b/docs/issue_template.md
@@ -1,6 +1,6 @@
-<!-- IF YOU DO NOT FOLLOW THE GUIDELINES, OR DO NOT USE THE TEMPLATE BELOW, YOUR ISSUE WILL BE CLOSED!
+<!-- IF YOU DO NOT FOLLOW THE GUIDELINES, OR DO NOT USE THE TEMPLATE BELOW, YOUR ISSUE WILL BE CLOSED! THIS APPLIES FOR BUG REPORTS AND FEATURE REQUESTS, NO EXCEPTIONS!
 
-The template below shows what you need to include in a good bug report, and you must use it. More information is available in the documentation: https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Filing-Issues.md
+The template below shows what you need to include in a good bug report, and you must use it. Feature requests don't need to include 'steps to reproduce' but the description and environment provide good context. More information is available in the documentation: https://github.com/baldurk/renderdoc/blob/v1.x/docs/CONTRIBUTING/Filing-Issues.md
 
 I'm happy to help, but you have to ensure I fully understand what you want and have the information I need. If you're unsure, please read the guide above for full information on what is expected for filing issues. -->
 
@@ -30,6 +30,6 @@ If you are able to share a capture, or your application, PLEASE DO THAT NOW beca
 
 * RenderDoc version: XXX
 * Operating System: XXX
-* API: XXX
+* Graphics API: XXX
 
 <!-- More details here never hurt! For example your GPU, driver version, etc. -->