Improved proposal instructions

Cybros · Dec 12, 2017 · 81e38b0 · 81e38b0
1 parent 26adc9a
commit 81e38b0
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/issue_template.md b/issue_template.md
@@ -2,12 +2,12 @@
 1. Replace this text with a clear statement of the problem that needs to be solved including any relevant supporting files.
 - If its a software abnormality, explain how it should act, how it does act, and how to reproduce it. 
 - **If you are reporting a security related problem,** DO NOT report here. Email [email protected] instead.
-2. Add a title in the field above that consisely summarizes the problem.
+2. Add a title in the field above that concisely summarizes the problem.
 
 ### My proposal
 3. If you have a solution to this problem and you will implement it, continue, otherwise remove the **my proposal** section.
 4. Replace this text with a clear statement of the solution you propose to implement, including any relevant supporting files. It can strengthen your proposal to include *pros* and *cons* and your thoughts about the *implications* (short and long term) of it being executed.
 
 <!--- Do not delete this section --->
-- - -
-**To break consensus** use [this template](https://gist.githubusercontent.com/markwhiting/ea8875602acd11e79002763735701503/raw/a8da103e23c07b74b4007459170104af04e38a33/break_consensus.md). You may also install this template to your account by following [these instructions](https://help.github.com/articles/creating-a-saved-reply/).
+---
+**Use comments to share your response** or use emoji 👍 to show your support. **To officially join in**, comment `I will help.` **To break consensus**, comment using [this template](https://gist.githubusercontent.com/markwhiting/ea8875602acd11e79002763735701503/raw/269916fe3c151cee51726f4f7f0488bec3010836/break_consensus.md). To find out more about this process, read the [how-to](https://gist.github.com/markwhiting/1fc8529fd074c12231c553936beec668).