another update to CONTRIBUTING.md

Author: leebyron

CONTRIBUTING.md

@@ -6,45 +6,15 @@ possible. Hopefully this document makes the process for contributing clear and
 answers any questions you may have. If not, feel free to open an
 [Issue](https://github.com/facebook/graphql/issues).
 
-## Getting Started
-
-1. Fork this repo by using the "Fork" button in the upper-right
-
-2. Check out your fork
-
-   ```sh
-   git clone [email protected]:yournamehere/graphql-js.git
-   ```
-
-3. Install all dependencies
-
-   ```sh
-   npm install
-   ```
-
-4. Get coding! If you've added code, add tests. If you've changed APIs, update
-   any relevant documentation or tests.
-
-5. Ensure all tests pass
-
-   ```sh
-   npm test
-   ```
-
-### Live Feedback
-
-While actively developing, we recommend running `npm run watch` in a terminal.
-This will watch the file system run any relevant lint, tests, and type checks automatically whenever you save a `.js` file.
-
-### Release on NPM
+## Issues
 
-*Only core contributors may release to NPM.*
+We use GitHub issues to track public bugs and requests. Please ensure your bug
+description is clear and has sufficient instructions to be able to reproduce the
+issue. The best way is to provide a reduced test case on jsFiddle or jsBin.
 
-To release a new version on NPM, use `npm version patch|minor|major` in order
-to increment the version in package.json and tag and commit a release. Then
-`git push --tags` this change so Travis CI can deploy to NPM. *Do not run
-`npm publish` directly.* Once published, add
-[release notes](https://github.com/graphql/graphql-js/tags). Use [semver](http://semver.org/) to determine which version to increment.
+Facebook has a [bounty program](https://www.facebook.com/whitehat/) 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.
 
 ## Pull Requests
 
@@ -66,15 +36,36 @@ to do this once to work on any of Facebook's open source projects.
 
 Complete your CLA here: <https://code.facebook.com/cla>
 
-## Issues
+### Getting Started
 
-We use GitHub issues to track public bugs and requests. Please ensure your bug
-description is clear and has sufficient instructions to be able to reproduce the
-issue. The best way is to provide a reduced test case on jsFiddle or jsBin.
+1. Fork this repo by using the "Fork" button in the upper-right
 
-Facebook has a [bounty program](https://www.facebook.com/whitehat/) 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.
+2. Check out your fork
+
+   ```sh
+   git clone [email protected]:yournamehere/graphql-js.git
+   ```
+
+3. Update or install all dependencies
+
+   ```sh
+   npm update
+   ```
+
+4. Get coding! If you've added code, add tests. If you've changed APIs, update
+   any relevant documentation or tests. Ensure your work is committed within a
+   feature branch.
+
+5. Ensure all tests pass
+
+   ```sh
+   npm test
+   ```
+
+### Live Feedback
+
+While actively developing, we recommend running `npm run watch` in a terminal.
+This will watch the file system run any relevant lint, tests, and type checks automatically whenever you save a `.js` file.
 
 ## Coding Style
 
@@ -87,6 +78,17 @@ outlined on that page and do not file a public issue.
 * Trailing commas,
 * Avd abbr wrds.
 
+## Release on NPM
+
+*Only core contributors may release to NPM.*
+
+To release a new version on NPM, first ensure all tests pass with `npm test`,
+then use `npm version patch|minor|major` in order to increment the version in
+package.json and tag and commit a release. Then `git push --tags` this change so
+Travis CI can deploy to NPM. *Do not run `npm publish` directly.*
+Once published, add [release notes](https://github.com/graphql/graphql-js/tags).
+Use [semver](http://semver.org/) to determine which version to increment.
+
 ## License
 
 By contributing to graphql-js, you agree that your contributions will be