Permalink
Browse files

DOC: fix two more typos, and add "add missing unit tests" as separate

contribution in maintenance work.
  • Loading branch information...
1 parent cd7184e commit ee502782f4e47a6cb3984cbf87a2057a081f825e @rgommers rgommers committed Apr 14, 2012
Showing with 9 additions and 9 deletions.
  1. +9 −9 doc/HOWTO_CONTRIBUTE.rst.txt
@@ -108,15 +108,15 @@ Contributing by helping maintain existing code
The previous section talked specifically about adding new functionality to
SciPy. A large part of that discussion also applies to maintenance of existing
code. Maintenance means fixing bugs, improving code quality or style,
-documenting existing functionality better, keeping build scripts up-to-date,
-etc. The SciPy `Trac`_ bug tracker contains all reported bugs,
-build/documentation issues, etc. Fixing issues described in Trac tickets helps
-improve the overall quality of SciPy, and is also a good way of getting
-familiar with the project. You may also want to fix a bug because you ran into
-it and need the function in question to work correctly.
-
-The discussion on code style and unit testing above apllies equally to bug
-fixes. It is usuallly best to start by writing a unit test that shows the
+documenting existing functionality better, adding missing unit tests, keeping
+build scripts up-to-date, etc. The SciPy `Trac`_ bug tracker contains all
+reported bugs, build/documentation issues, etc. Fixing issues described in
+Trac tickets helps improve the overall quality of SciPy, and is also a good way
+of getting familiar with the project. You may also want to fix a bug because
+you ran into it and need the function in question to work correctly.
+
+The discussion on code style and unit testing above applies equally to bug
+fixes. It is usually best to start by writing a unit test that shows the
problem, i.e. it should pass but doesn't. Once you have that, you can fix the
code so that the test does pass. That should be enough to send a PR for this
issue. Unlike when adding new code, discussing this on the mailing list may

0 comments on commit ee50278

Please sign in to comment.