fix headers

Author: cldougl

contributing.md

@@ -1,8 +1,8 @@
 The bottom line. Follow your Nose, or our Nose. Write-run-love tests :fist:.
 
-##Setup
+## Setup
 
-###Fork, Clone, Setup Your Version of the Plotly Python API
+### Fork, Clone, Setup Your Version of the Plotly Python API
 
 First, you'll need to *get* our project. This is the appropriate *clone* command (if you're unfamiliar with this process, https://help.github.com/articles/fork-a-repo):
 
@@ -12,7 +12,7 @@ First, you'll need to *get* our project. This is the appropriate *clone* command
 git clone https://github.com/plotly/python-api.git
 ```
 
-###Submodules
+### Submodules
 
 Second, this project uses git submodules! They're both helpful and, at times, difficult to work with. The good news is you probably don't need to think about them! Just run the following shell command to make sure that your local repo is wired properly:
 
@@ -35,7 +35,7 @@ Additionally, there are some project shortcuts that live in the `makefile` file.
 make readme
 ```
 
-###Making a Development Branch
+### Making a Development Branch
 
 Third, *don't* work in the `master` branch. As soon as you get your master branch ready, run:
 
@@ -46,22 +46,22 @@ git checkout -b my-dev-branch
 
 ... where you should give your branch a more descriptive name than `my-dev-branch`
 
-###Pull Request When Ready
+### Pull Request When Ready
 
 Once you've made your changes (and hopefully written some tests...), make that pull request!
 
-##Suggestions
+## Suggestions
 
-###Local Python
+### Local Python
 Setting up Python versions that *don't* require you to use `sudo` is a good idea. In addition, the core Python on your machine may not be the Python that we've developed in! Here are some nice guides for Mac, Windows, and Linux: 
 - http://docs.python-guide.org/en/latest/starting/install/osx/
 - http://docs.python-guide.org/en/latest/starting/install/win/
 - http://docs.python-guide.org/en/latest/starting/install/linux/
 
-###Virtualenv
+### Virtualenv
 Virtualenv is a way to create Python environments on your machine that know nothing about one another. This is really helpful for ironing out dependency-problems arising from different versions of packages. Here's a nice guide on how to do this: http://docs.python-guide.org/en/latest/dev/virtualenvs/
 
-###Alter Your PYTHONPATH
+### Alter Your PYTHONPATH
 The PYTHONPATH variable in your shell tells Python where to look for modules. Since you'll be developing, it'll be a pain to need to *install* Python every time you need to test some functionality (or at least ensure you're running code from the right directory...). You can easily make this change from a shell:
 
 ```bash
@@ -70,7 +70,7 @@ export PYTHONPATH="/path/to/local/repo:$PYTHONPATH"
 
 Note, that's non-permanent. When you close the shell, that variable definition disappears. Also, `path/to/local/repo` is *your* specific repository path (e.g., `/Users/andrew/projects/python-api`).
 
-###Why?
+### Why?
 
 Now you can run the following code and be guaranteed to have a working development version that you can make changes to on-the-fly, test, and be confident will not break on other's machines!
 
@@ -80,11 +80,11 @@ pip install -r optional-requirements.txt
 export PYTHONPATH="/path/to/local/repo:$PYTHONPATH"
 ```
 
-##Dependencies
+## Dependencies
 
 There's a short list of core dependencies you'll need installed in your Python environment to have any sort of fun with Plotly's Python API (see `requirements.txt`). Additionally, you're likely to have even more fun if you install some other requirements (see `optional-requirements.txt`). 
 
-###Dependencies and Virtualenv
+### Dependencies and Virtualenv
 
 If you decided to follow the suggestion about about the Virtualenv *and* you've run `source bin/activate` within your new virtualenv directory to activate it--you can run the following to install the core dependencies:
 
@@ -98,14 +98,14 @@ To install the optional dependencies:
 pip install -r optional-requirements.txt
 ```
 
-##Testing
+## Testing
 
 We take advantage of two tools to run tests:
 
 * [`tox`](https://tox.readthedocs.io/en/latest/), which is both a virtualenv management and test tool.
 * [`nose`](https://nose.readthedocs.org/en/latest/), which is is an extension of Python's unittest
 
-###Running Tests with `nose`
+### Running Tests with `nose`
 
 Since our tests cover *all* the functionality, to prevent tons of errors from showing up and having to parse through a messy output, you'll need to install `optional-requirements.txt` as explained above.
 
@@ -133,7 +133,7 @@ nosetests -w plotly/tests/test_plotly
 nosetests plotly/tests/test_plotly/test_plot.py
 ```
 
-###Running tests with `tox`
+### Running tests with `tox`
 
 Running tests with tox is much more powerful, but requires a bit more setup.
 
@@ -174,7 +174,7 @@ Note that anything after `--` is substituted in for `{posargs}` in the tox.ini.
 tox -- -a '!slow','!matplotlib'
 ```
 
-###Writing Tests
+### Writing Tests
 
 You're *strongly* encouraged to write tests that check your added functionality.