Grammar nazi

(PS: Great tool, thanks!)

Author: mikemee

docs/contributing.rst

@@ -33,7 +33,7 @@ Contributors should use the following roadmap to guide them through the process
 #. Comment on the ticket letting everyone know you're going to be hacking on it so that nobody duplicates your effort. It's also good practice to provide some general idea of how you plan on resolving the issue so that other developers can make suggestions.
 #. Write tests for the feature you're building. Follow the format of the existing tests in the test directory to see how this works. You can run all the tests with the command ``nosetests``. The one exception to testing is command-line scripts. These don't need unit test, though all reusable components should be factored into library modules.
 #. Write the code. Try to stay consistent with the style and organization of the existing codebase. A good patch won't be refused for stylistic reasons, but large parts of it may be rewritten and nobody wants that. 
-#. As your coding, periodically merge in work from the master branch and verify you haven't broken anything by running the test suite.
+#. As you're coding, periodically merge in work from the master branch and verify you haven't broken anything by running the test suite.
 #. Write documentation for user-facing features (and library features once the API has stabilized).
 #. Once it works, is tested, and has documentation, submit a pull request on Github.
 #. Wait for it to either be merged or to recieve a comment about what needs to be fixed.