Improve copy in CONTRIBUTING.md

Reflect some of the recent changes in necolas/issue-guidelines that tidy up the language and simplify parts of the guidelines.

Author: necolas

CONTRIBUTING.md

@@ -4,36 +4,31 @@
 Thanks! There are plenty of ways you can help!
 
 
-## Reporting issues
+## Bugs
 
 A bug is a _demonstrable problem_ that is caused by the code in the
-repository.
+repository. Good bug reports are extremely helpful - thank you!
 
-Please read the following guidelines before you [report an issue](https://github.com/h5bp/html5-boilerplate/issues/):
+Guidelines for bug reports:
 
 1. **Use the GitHub issue search** — check if the issue has already been
- reported. If it has been, please comment on the existing issue.
+ reported.
 
-2. **Check if the issue has been fixed** — the latest `master` or
- development branch may already contain a fix.
+2. **Check if the issue has been fixed** — try to reproduce it using the
+ latest `master` branch in the repository.
 
-3. **Isolate the demonstrable problem** — make sure that the code in the
- project's repository is _definitely_ responsible for the issue. Create a
- [reduced test case](http://css-tricks.com/6263-reduced-test-cases/) - an
- extremely simple and immediately viewable example of the issue.
+3. **Isolate the problem** — ideally create a [reduced test
+ case](http://css-tricks.com/6263-reduced-test-cases/) and a live example.
 
-4. **Include a live example** — provide a link to your reduced test case
- when appropriate (e.g. if the issue is related to (front-end technologies).
- Please use [jsFiddle](http://jsfiddle.net) to host examples.
-
-Please try to be as detailed as possible in your report too. What is your
-environment? What steps will reproduce the issue? What browser(s) and OS
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
 experience the problem? What would you expect to be the outcome? All these
-details will help people to assess and fix any potential bugs.
+details will help people to fix any potential bugs.
 
-### Example of a good bug report:
+Example:
 
-> Short and descriptive title
+> Short and descriptive example bug report title
 >
 > A summary of the issue and the browser/OS environment in which it occurs. If
 > suitable, include the steps required to reproduce the bug.
@@ -49,53 +44,75 @@ details will help people to assess and fix any potential bugs.
 > causing the bug, and potential solutions (and your opinions on their
 > merits).
 
-A good bug report shouldn't leave people needing to chase you up to get further
-information that is required to assess or fix the bug.
-
 **[File a bug report](https://github.com/h5bp/html5-boilerplate/issues/)**
 
 
 ## Pull requests
 
-Good pull requests — patches, improvements, new features — are a fantastic
+Good pull requests - patches, improvements, new features - are a fantastic
 help. They should remain focused in scope and avoid containing unrelated
-commits.
-
-If your contribution involves a significant amount of work or substantial
+commits. If your contribution involves a significant amount of work or substantial
 changes to any part of the project, please open an issue to discuss it first.
 
+Make sure to adhere to the coding conventions used throughout a project
+(indentation, accurate comments, etc.). Please update any documentation that is
+relevant to the change you're making.
+
 Please follow this process; it's the best way to get your work included in the
 project:
 
-1. [Fork](http://help.github.com/fork-a-repo/) the project.
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
+ and configure the remotes:
 
-2. Clone your fork (`git clone
- https://github.com/<your-username>/html5-boilerplate.git`).
+ ```bash
+ # Clones your fork of the repo into the current directory in terminal
+ git clone https://github.com/<your-username>/html5-boilerplate.git
+ # Navigate to the newly cloned directory
+ cd html5-boilerplate
+ # Assigns the original repo to a remote called "upstream"
+ git remote add upstream https://github.com/h5bp/html5-boilerplate.git
+ ```
 
-3. Add an `upstream` remote (`git remote add upstream
- https://github.com/h5bp/html5-boilerplate.git`).
+2. If you cloned a while ago, get the latest changes from upstream:
 
-4. Get the latest changes from upstream (e.g. `git pull upstream
- <dev-branch>`).
+ ```bash
+ git checkout master
+ git pull upstream master
+ ```
 
-5. Create a new topic branch to contain your feature, change, or fix (`git
- checkout -b <topic-branch-name>`).
+3. Create a new topic branch to contain your feature, change, or fix:
 
-6. Make sure that your changes adhere to the current coding conventions used
- throughout the project - indentation, accurate comments, etc. Please update
- any documentation that is relevant to the change you are making.
+ ```bash
+ git checkout -b <topic-branch-name>
+ ```
 
-7. Commit your changes in logical chunks; use git's [interactive
- rebase](https://help.github.com/articles/interactive-rebase) feature to tidy
- up your commits before making them public. Please adhere to these [git commit
+4. Commit your changes in logical chunks. Please adhere to these [git commit
  message
  guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
- or your pull request is unlikely be merged into the main project.
+ or your pull request is unlikely be merged into the main project. Use git's
+ [interactive rebase](https://help.github.com/articles/interactive-rebase)
+ feature to tidy up your commits before making them public.
+
+5. Locally merge (or rebase) the upstream development branch into your topic branch:
 
-8. Locally merge (or rebase) the upstream branch into your topic branch.
+ ```bash
+ git pull [--rebase] upstream master
+ ```
 
-9. Push your topic branch up to your fork (`git push origin
- <topic-branch-name>`).
+6. Push your topic branch up to your fork:
+
+ ```bash
+ git push origin <topic-branch-name>
+ ```
 
 10. [Open a Pull Request](http://help.github.com/send-pull-requests/) with a
- clear title and description. Please mention which browsers you tested in.
+ clear title and description.
+
+
+## Do not…
+
+Please **do not** use the issue tracker for personal support requests (use
+[StackOverflow](http://stackoverflow.com/questions/tagged/html5boilerplate) or IRC).
+
+Please **do not** derail or troll issues. Keep the
+discussion on topic and respect the opinions of others.