Add in suggestions from #58 and wrap long lines

Author: katbow

CONTRIBUTING.md

@@ -1,40 +1,40 @@
 [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/codingforeveryone/js?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
-You can find details for each step here. Look for the step you are having issues on for full instructions. If you still have questions, check out the Gitter channel!
-
-1. **Find** an unsolved problem titled "new-member-x" under [Issues](../../issues). If none exist, ask for one by creating a new issue with the title "New member in need of a problem".
-1. **Reserve** the issue by commenting that you intend to solve the problem, or assigning it to yourself.
-1. **Solve** the problem locally.
-* **Create a branch** with a descriptive name (e.g. new-member-x).
-  - To create a branch, click on the repo name (js), then click on the "Branch: master" button, and type in the new branch name
+You can find details for each step here. Look for the step you are having
+issues on for full instructions. If you still have questions, check out the Gitter channel!
+
+1. **Find** an unsolved problem titled "new-member-x" under [Issues](../../issues)
+ or if none exist, create a new issue asking for one
+  - This can have a title such as 'New member in need of a problem'
+1. **Reserve** the issue by commenting that you intend to
+solve the problem, or assigning it to yourself
+1. **Solve** the problem locally
+1. **Create a branch** with a descriptive name (e.g. new-member-x)
+  - To create a branch, click on the repo name (js), then click on the
+  "Branch: master" button, and type in the new branch name
 1. **Push** your solution to the newly created branch.
-  - See resources at the bottom of the page for more info on how to do this.
-1. **Create a pull request** to allow someone to merge your solution onto the repo.
-  - Click on the green pull request button which is next to the new branch button.
-  - Set the "base" to "master" and the "compare" to your new branch name.
-  - Someone will merge your pull request after they double check that your solution is correct.
-1. **Post a new simple JS problem** titled "new-member-x+1" under Issues for the next person to practice. Keep the problem simple!
+  - See resources at the bottom of the page for more info on how to do this
+1. **Create a pull request** to allow someone to merge your solution onto the repo
+  - Click on the green pull request button which is next to the new branch button
+  - Set the "base" to "master" and the "compare" to your new branch name
+  - Someone will merge your pull request after they double check that your solution is correct
+1. **Post a new *simple* JS problem** titled "new-member-x+1" under Issues for
+the next person to practice.
+  - Keep the problem simple! Have a look at 8kyu and 7kyu Katas on Codewars for inspiration.
 
 ### If you have any suggestions for this repo:
 
-* feel free to post them in an issue
-* or make a pull request with your changes
-* please be descriptive in your comments!
+- feel free to post them in an issue
+- or make a pull request with your changes
+- please be descriptive in your comments!
 
 Before the changes are merged make sure there's at least a short discussion about them first.
 
 ### Resources:
-**Here's a good read on Git:**
-
-https://github.com/NataliaLKB/learn-git-basics
-
-**A nice tutorial on resolving conflicts when merging
-
-http://www.gitguys.com/topics/merging-with-a-conflict-conflicts-and-resolutions/
+[**Youtube introduction to GitHub (30 minutes)**](https://www.youtube.com/playlist?list=PLfdtiltiRHWFEbt9V04NrbmksLV4Pdf3j)
 
-**Youtube introduction to GitHub (30 minutes)**
+[**A good read on Git**](https://github.com/NataliaLKB/learn-git-basics)
 
-https://www.youtube.com/playlist?list=PLfdtiltiRHWFEbt9V04NrbmksLV4Pdf3j
+[**GitHub help on 'Fork a repo'**](https://help.github.com/articles/fork-a-repo/)
 
-**GitHub help on 'Fork a repo'**
-https://help.github.com/articles/fork-a-repo/
+[**A nice tutorial on resolving conflicts when merging**](http://www.gitguys.com/topics/merging-with-a-conflict-conflicts-and-resolutions/)