From 3a38b0e6c3f992fa0a433acd9bee5af2cab099d5 Mon Sep 17 00:00:00 2001
From: Molly <momack2@users.noreply.github.com>
Date: Mon, 12 Nov 2018 14:17:30 -0800
Subject: [PATCH] updates for spacing and readability

---
 ISSUE_TEMPLATE.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
index dcd013012..dd1568de6 100644
--- a/ISSUE_TEMPLATE.md
+++ b/ISSUE_TEMPLATE.md
@@ -1,11 +1,11 @@
-<!-- 🔥❓ If you have a *QUESTION* about IPFS, please direct it to our forum at https://discuss.ipfs.io. 🔥❓
+<!-- 🔥❓If you have a *QUESTION* about IPFS, please ask on our forum at https://discuss.ipfs.io 🔥❓
 
-The go-ipfs issues are *only for bug reports and directly actionable feature requests*. Please direct all other questions, ideas, or suggestions to our discuss forum. Remember to search the issue tracker for an existing report concerning your issue before posting, and see https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. -->
+The go-ipfs issues are *only* for bug reports and directly actionable feature requests. Please direct all other questions, ideas, or suggestions to our discuss forum. Remember to search the issue tracker for an existing report concerning your issue before posting, and see https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. -->
 
 #### Version information:
 <!-- Output From `ipfs version --all`
 
-Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary, report back if the problem persists. -->
+Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary. Report back if the problem persists. -->
 
 #### Type:
 <!-- Bug, Feature, Enhancement, Etc -->
@@ -13,7 +13,7 @@ Please check dist.ipfs.io for a newer version of go-ipfs and update if necessary
 #### Description:
 <!-- This is where you get to tell us what went wrong or your specific feature request. When doing so, please make sure to include *all* relevant information.
 
-When _reporting a bug_, please try to include:
+When reporting a _bug_, please try to include:
   * What you were doing when you experienced the bug.
   * Any error messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
   * When possible, steps to reliably produce the bug.