From 2ec757e26edf98ed1730520ebaafcbf308c903ec Mon Sep 17 00:00:00 2001
From: Dave Grochocki <grochocki@users.noreply.github.com>
Date: Fri, 5 Apr 2019 12:51:18 -0700
Subject: [PATCH] Update feature_request.md

---
 .github/ISSUE_TEMPLATE/feature_request.md | 38 ++++++++++++-----------
 1 file changed, 20 insertions(+), 18 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 13e593bb..9c761144 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -8,34 +8,36 @@ assignees: ''
 ---
 
 <!--
-
-See https://github.com/Microsoft/calculator/blob/master/docs/NewFeatureProcess.md for
-suggestions on how to write a good feature pitch. Just want to submit an idea quickly? Try Feedback
-Hub instead: https://insider.windows.com/en-us/fb/?contextid=130
-
+See https://github.com/Microsoft/calculator/blob/master/docs/NewFeatureProcess.md for suggestions on how to write a good feature pitch. Just want to submit an idea quickly? Try Feedback Hub instead: https://insider.windows.com/en-us/fb/?contextid=130
 -->
 
 **Problem Statement**
-<!-- What problem are we trying to solve? Who’s the target audience? Is there a customer need or
-pain point we need to remedy? Is there a business goal or metric we are trying to improve? Do we
-have a hypothesis we want to prove or disprove? -->
+<!--
+What problem are we trying to solve? Who’s the target audience? Is there a customer need or pain point we need to remedy? Is there a business goal or metric we are trying to improve? Do we have a hypothesis we want to prove or disprove? 
+-->
 
 **Evidence or User Insights**
-<!-- Why should we do this? Potential sources of data: Feedback Hub, other GitHub issues, other
-anecdotes from listening to customers in person or online, request from another team, telemetry
-data, user research, market or competitive research -->
+<!--
+Why should we do this? Potential sources of data: Feedback Hub, other GitHub issues, other anecdotes from listening to customers in person or online, request from another team, telemetry data, user research, market or competitive research
+-->
 
 **Proposal**
-<!-- How will the solution/feature help us solve the problem? How will it meet the target
-audience’s needs? If there are business goals or metrics, how does this improve them? -->
+<!--
+How will the solution/feature help us solve the problem? How will it meet the target audience’s needs? If there are business goals or metrics, how does this improve them?
+-->
 
 **Goals**
-<!-- What you want to accomplish with this feature. Typical examples include
-“User Can *perform some task*” -->
+<!--
+What you want to accomplish with this feature. Typical examples include
+“User Can *perform some task*”
+-->
 
 **Non-Goals**
-<!-- Things we are explicitly not doing or supporting or that are out of scope, including reasons
-why. -->
+<!--
+Things we are explicitly not doing or supporting or that are out of scope, including reasons why.
+-->
 
 **Low-Fidelity Concept**
-<!-- Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage. -->
+<!--
+Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage.
+-->