summaryrefslogtreecommitdiff
path: root/doc/contribute.rst
diff options
context:
space:
mode:
authorClaudiu Popa <cpopa@cloudbasesolutions.com>2014-11-12 22:26:04 +0200
committerClaudiu Popa <cpopa@cloudbasesolutions.com>2014-11-12 22:26:04 +0200
commitaf213f498b2ec2fea079cef508135949b724ceaf (patch)
tree01cefc93ff9855ff777b028d2f9814f97fda34d9 /doc/contribute.rst
parent29ee4406d2ad7ee222be1673f5e675267c123c09 (diff)
downloadpylint-af213f498b2ec2fea079cef508135949b724ceaf.tar.gz
Cleanup through documentation.
Diffstat (limited to 'doc/contribute.rst')
-rw-r--r--doc/contribute.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/contribute.rst b/doc/contribute.rst
index 6a45dea..43e5dfb 100644
--- a/doc/contribute.rst
+++ b/doc/contribute.rst
@@ -47,7 +47,7 @@ http://lists.logilab.org/pipermail/python-projects/
Forge
-----
-Pylint is developped using the mercurial_ distributed version control system.
+Pylint is developed using the mercurial_ distributed version control system.
You can clone Pylint and its dependencies from ::
@@ -64,7 +64,7 @@ your patch gets accepted.
- Pylint keeps a set of unit tests in the /test directory. The
`test_func.py` module uses external files to have some kind of easy
- functionnal testing. To get your patch accepted you must write (or change)
+ functional testing. To get your patch accepted you must write (or change)
a test input file in the `test/input` directory and message file in the
`test/messages` directory. Then run `python test_func.py` to ensure that
your test is green.
@@ -117,7 +117,7 @@ without installing them. You can run all the unit tests like so::
The -S flag keeps distutils from interfering with sys.path. YMMV.
-Adding new functionnal tests
+Adding new functional tests
----------------------------
Pylint comes with an easy way to write functional tests for new checks: