Update CONTRIBUTING.md (#1244)

Fixed line breaks for MarkDown rule.

Author: JeffGuKang

CONTRIBUTING.md

@@ -1,9 +1,11 @@
 # Contributing to the Parse JavaScript SDK
+
 We want to make contributing to this project as easy and transparent as possible.
 
 If you're looking to get started, but want to ease yourself into the codebase, look for issues tagged [good first task](https://github.com/parse-community/Parse-SDK-JS/labels/good%20first%20task). These are simple yet valuable tasks that should be easy to get started.
 
 ## `master` is unsafe
+
 Our goal is to keep `master` stable, but there may be changes that your application may not be compatible with. We'll do our best to publicize any breaking changes, but try to use our specific releases in any production environment.
 
 ## Setting up the project for debugging and contributing:
@@ -63,6 +65,7 @@ To run the integration tests, you will need a valid mongodb running on your loca
 Use `npm run integration` in order to run the integration tests. If you have the vscode Jasmine extension installed (as recommended), you can run your tests by clicking the *Run* or the *Debug* lens that appears near by the test.
 
 ### Pull Requests
+
 We actively welcome your pull requests. When we get one, we'll run some Parse-specific integration tests on it first. From here, we'll need to get a core member to sign off on the changes and then merge the pull request. For API changes we may need to fix internal uses, which could cause some delay. We'll do our best to provide updates and feedback throughout the process.
 
 1. Fork the repo and create your branch from `master`.
@@ -72,9 +75,11 @@ We actively welcome your pull requests. When we get one, we'll run some Parse-sp
 5. Make sure your code lints.
 
 ### Known Issues
+
 We use GitHub issues to track public bugs. We will keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new issue, try to make sure your problem doesn't already exist.
 
 ### Reporting New Issues
+
 Not all issues are SDK issues. If you're unsure whether your bug is with the SDK or backend, you can test to see if it reproduces with our [REST API][rest-api] and [Parse API Console][parse-api-console]. If it does, you can report backend bugs [here][bug-reports].
 If the issue only reproduces with the JS SDK, you can [open an issue](https://github.com/parse-community/parse-server/issues) on this repository.
 
@@ -87,9 +92,11 @@ Details are key. The more information you provide us the easier it'll be for us
 * Anything else you find relevant.
 
 ### Security Bugs
+
 Parse Community has a [responsible Vulnerability Disclosure Program](https://github.com/parse-community/parse-server/blob/master/SECURITY.md) for the safe disclosure of security bugs. In those cases, please go through the process outlined on that page and do not file a public issue.
 
 ## Coding Style
+
 * Most importantly, match the existing code style as much as possible.
 * We use [Flow](http://flowtype.org/) and ES6 for this codebase. Use modern syntax whenever possible.
 * Keep lines within 80 characters.
@@ -100,6 +107,7 @@ Parse Community has a [responsible Vulnerability Disclosure Program](https://git
 This project adheres to the [Contributor Covenant Code of Conduct](https://github.com/parse-community/parse-server/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to honor this code.
 
 ## License
+
 By contributing to the Parse JavaScript SDK, you agree that your contributions will be licensed under its license.
 
  [google-group]: https://groups.google.com/forum/#!forum/parse-developers