touch up pull request guidelines

CONTRIBUTING.md

@@ -17,9 +17,11 @@ Then review and decide what upgrades to make, if any.
 Changes to `requirements.txt` should always be by pull request.
 
 ## Code Standards
+
 ### Testing
 - Add tests for every change made
 - Tests should be realistic and exercise a wide range of possibilities
+
 ### Docstrings
 - Use [Google Style Docstrings](http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html).
 - Add docstrings to all functions with a one-line description of its purpose.

PULL_REQUEST_TEMPLATE.md

 
 
-### Checklist for Reviewer(s)
+### Tips for Review
 
-- [ ] Tests were added to cover all code changed
-- [ ] Documentation was added / updated 
-- [ ] Code and tests follow standards in CONTRIBUTING.md
-- [ ] A detailed explanation of issues was given by the reviewer, using clear language and technical terms
+- Tests were added to cover all code changed
+- Documentation was added / updated
+- Code and tests follow standards in CONTRIBUTING.md
+- A detailed explanation of issues was given by the reviewer, using clear language and technical terms