spelling; whitespace

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # How to contribute
 
-## Issue Submission Guidlines
+## Issue Submission Guidelines
 
 * Because of the volume of requests, we do not use the issue tracker for support questions. If you are trying to get a particular effect or you have a problem with your code, please ask your question on stackoverflow.com or the [user group](https://groups.google.com/forum/?fromgroups#!forum/dc-js-user-group)
 * It will be far, far easier for others to understand your problem or bug if you demonstrate it with a short example on http://jsfiddle.net/ or on http://bl.ocks.org/ (http://blockbuilder.org/ is a great way to edit bl.ocks!). Here are some examples you can fork to get started:
@@ -14,7 +14,7 @@
 
 ## Pull Request Guidelines
 
-* Fork the repository. 
+* Fork the repository.
 * As with all pull requests, put your changes in a branch. For contributions that change the dc.js API, create your branch off of `develop`. If your contribution does not change the API, branch off of `master` instead.
 * Make changes to the files in `src/` not dc.js
 * Add tests to `spec/`. Feel free to create a new file if needed.
@@ -23,7 +23,7 @@
 * Run `grunt lint` to confirm that your code meets the dc.js style guidelines.
 * Run `grunt test` to confirm that all tests will pass on phantomjs.
 * Commit your changes to `src/*` and `spec/*` but not any build artifacts.  (Build artifacts include `dc.*js*`, `web/docs/*`, `web/js/*`)
-* Submit a pull request. 
+* Submit a pull request.
 * If you merge `develop` or `master` into your patchset, please rebase against develop. (It's okay to rewrite history for PRs, because these branches are temporary and it's unlikely that anyone is tracking your feature branch.)
 * The DC maintainer team will review and build the artifacts when merging.
 * If you continue making changes to your fork of `dc.js`, create a separate branch for each pull request and keep the changes separate.
@@ -50,4 +50,3 @@ Or you can just run the commands manually before committing.
 
 Running `grunt server` will host the jasmine specs at http://localhost:8888/spec.
 Please use `.transitionDuration(0)` for all chart tests.
-