Refactor/cleanup GitHub templates (#102)

Refactor/cleanup GitHub templates

.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,9 +1,12 @@
 ---
 name: Bug Report
-about: Use this to report a new bug
+about: Use this to report a bug or content-related typo/mistake
 
 ---
 
+<!--- Provide a short summary of the issue in the Title above -->
+<!--- Fill in below the sections that are applicable to the issue -->
+
 ### Expected Behavior
 <!--- Tell us what should happen -->
 
@@ -14,15 +17,5 @@ about: Use this to report a new bug
 <!--- Not obligatory, but suggest a fix/reason for the bug, -->
 
 ### Steps to Reproduce
-<!--- Provide a link to a live example, or an unambiguous set of steps to -->
-<!--- reproduce this bug. Include code to reproduce, if relevant -->
-1.
-2.
-3.
-4.
-
-### Context (Environment)
-<!--- How has this issue affected you? What are you trying to accomplish? -->
-<!--- Providing context helps us come up with a solution that is most useful in the real world -->
-
-<!--- Provide a general summary of the issue in the Title above -->
+<!--- Provide a link to a live example, or an unambiguous set of (preferably) -->
+<!--- enumerated steps to reproduce this bug. Include code to reproduce, if relevant -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,39 +1,8 @@
-<!-- Lines like this one are comments and will not be shown in the final output. -->
-<!-- Make sure that you have read the "Contributing" section of the README and also the notes in CodingStyle. -->
-<!-- If you are a collaborator, please add labels and assign other collaborators for a review. -->
+**Related issue(s) and PR(s)**
+This PR closes [issue number].
 
-### Describe the pull request:
-<!-- Replace [ ] with [x] to select options. -->
-- [ ] Bug fix
-- [ ] Functional change
-- [ ] New feature
-- [ ] Code cleanup
-- [ ] Build system change
-- [ ] Documentation change
-- [ ] Language translation
 
-### Pull request long description:
-<!-- Describe your pull request in detail. -->
+**Description**
 
-### Changes made:
-<!-- Enumerate the changes with 1), 2), 3) etc. -->
-<!-- Ensure the test cases are updated if needed. -->
 
-### Related issues:
-<!-- Reference issues with #<issue-num>. -->
-<!-- Write "Fixes #<issue-num>" to notify Github that this PR fixes an issue. -->
-
-### Additional information:
-<!-- Include sample dive log or other relevant information to allow testing the change where feasible. -->
-
-### Release note:
-<!-- Describe if this change needs a release note present in CHANGELOG.md. -->
-<!-- Also, please make sure to add the release note on top of the file CHANGELOG.md. -->
-
-### Documentation change:
-<!-- If this PR makes changes to user functionality, then the documentation has to be updated too. -->
-<!-- Please, briefly outline here what has changed in terms of the user experience (UX). -->
-<!-- If UX changes have been made, a maintainer should apply the 'needs-documentation-change' label. -->
-
-### Mentions:
-<!-- Mention users that you want to review your pull request with @<user-name>. Leave empty if not sure. -->
+**How to test**