Merge pull request #65 from 4-20ma/64-cleanup-template-wording

Fix #64 clean up templates

.github/ISSUE_TEMPLATE.md

@@ -46,17 +46,21 @@ Refer to [What's in a Story?](https://dannorth.net/whats-in-a-story/)
 
 #### Narrative:
 <!-- Replace role, feature, benefit. -->
+```` text
 As a [role]
 I want [feature]
 So that [benefit]
+````
 
 #### Acceptance Criteria:
 <!--
 Present as one or more Scenarios, replacing context, event, outcome.
 -->
+```` text
 Scenario 1: Title
 Given [context]
   And [some more context]...
 When  [event]
 Then  [outcome]
   And [another outcome]...
+````

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,10 +6,10 @@ Provide the following information for all issues. Replace [brackets] and placeho
 (QUESTIONS, BUG REPORTS, FEATURE REQUESTS).
 -->
 ### Description
-[Describe what this change achieves; include Fixes #xxx or Closes #xxx (where xxx is issue number) in description]
+[Describe what this change achieves]
 
 ### Issues Resolved
-[List any existing issues this PR resolves]
+[List any existing issues this PR resolves; include Fixes #xxx or Closes #xxx (where xxx is issue number)]
 
 ### Check List
 

CONTRIBUTING.md

@@ -32,7 +32,7 @@ Project maintainers assign labels to Issues and Pull Requests (PRs) to categoriz
 - `Bug` - existing code does not behave as described in the project documentation; _requires_ clear test case and be _reproducible_ by project maintainer
 - `Enhancement` - minor modification to an existing feature
 - `Feature Requst` - new functionality; _requires_ a well-written, clear user story
-- 'Maintenance` - minor administrative change that does not provide enhancement or introduce new feature
+- `Maintenance` - minor administrative change that does not provide enhancement or introduce new feature
 - `Question` - self-explanatory
 
 #### Priority