Docs: squash 3 - more inconsistancies and fixes

Author: lukeapage

CONTRIBUTING.md

@@ -16,20 +16,20 @@ This is the best way to contribute to jQuery UI. Please read through the full gu
 
 Every week (unless otherwise noted) the jQuery UI team has a meeting to discuss the progress of current work and to bring forward possible new blockers for discussion. The meeting is held on [IRC](http://irc.jquery.org) in the #jquery-meeting channel at [Noon EST](http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=17&year=2011&hour=12&min=0&sec=0&p1=43) on Wednesdays. Meeting notes are posted on http://meetings.jquery.org/category/ui/ after each meeting.
 
-## Tips For Bug Patching
+## Tips for Getting Started
 
-### Environment: minimum required
+### Environment: Minimum Required
 
-If you are contributing changes you will need a fork of jquery (see [Getting the source](environment-getting-the-source)). If you just want the source code you could clone jquery ui directly:
+If you are contributing changes you will need a fork of jquery (see [Getting the Source](#environment-getting-the-source)). If you just want the source code you could clone jquery ui directly:
 
 ```bash
 git clone git://github.com/jquery/jquery-ui.git
 cd jquery-ui
 ```
 
-The tests can run in any local web server. Ideally you should test your patch in appropriate web browsers and if possible run `grunt` to lint the code and run automated tests (this will happen automatically when you create a pull request). See the [full setup](environment-recommended-setup) for setting up Node.js so that the grunt command works.
+The tests can run in any local web server. Ideally you should test your patch in appropriate web browsers and if possible run `grunt` to lint the code and run automated tests (this will happen automatically when you create a pull request). See the [recommended setup](#environment-recommended-setup) for setting up Node.js so that the grunt command works.
 
-### Environment: Getting the source
+### Environment: Getting the Source
 
 * Create a fork of the jQuery UI repo on GitHub at http://github.com/jquery/jquery-ui. This will create a fork of jquery-ui at your username.
 * You may want to clone jquery-ui under the path to your web server. If so, change to the required directory
@@ -59,7 +59,7 @@ git remote add upstream git://github.com/jquery/jquery-ui.git
 git pull upstream master
 ```
 
-### Environment: Recommended setup
+### Environment: Recommended Setup
 
 jQuery UI uses Node.js & Grunt to automate the building and validation of source code. Here is how to set that up:
 
@@ -86,7 +86,7 @@ Linux: [Setting up LAMP](https://www.linux.com/learn/tutorials/288158-easy-lamp-
 [Mongoose (most platforms)](http://code.google.com/p/mongoose/)
 [http-server](https://www.npmjs.com/package/http-server)
 
-### Running the tests
+### Running the Tests
 
 To lint the JavaScript, HTML, and CSS, as well as run a smoke test in PhantomJS, run grunt:
 
@@ -98,6 +98,6 @@ To run the tests for a specific plugin in your browser, open the appropriate fil
 
 Ideally you would test in all of our [supported browsers](http://jqueryui.com/browser-support/), but if you don't have all of these browsers available, that's ok.
 
-### Before making a pull request
+### Before Making a Pull Request
 
 Make sure to read our [commits and pull requests documentation](http://dev.contribute.jquery.org/commits-and-pull-requests/) for full details on working with branches and forks, as well as our commit guidelines.

README.md

@@ -10,7 +10,7 @@ If you are interested in helping develop jQuery UI, you are in the right place.
 To discuss development with team members and the community, visit the [Developing jQuery UI Forum](http://forum.jquery.com/developing-jquery-ui) or [#jqueryui-dev on irc.freenode.net](http://irc.jquery.org/).
 
 
-## For contributors
+## For Contributors
 
 If you want to help and provide a patch for a bugfix or new feature, please take
 a few minutes and look at [our Getting Involved guide](http://wiki.jqueryui.com/w/page/35263114/Getting-Involved).