diff --git a/docs/intro/community.rst b/docs/intro/community.rst index 5b72ac27f..afb4c5ec1 100644 --- a/docs/intro/community.rst +++ b/docs/intro/community.rst @@ -19,7 +19,7 @@ The mission of the Python Software Foundation is to promote, protect, and advanc PEPs ---- -PEPs are *Python Enhancement Proposals*. They are define change to Python itself, or the standards around it. +PEPs are *Python Enhancement Proposals*. They define changes to Python itself, or the standards around it. There are three different types of PEPs (as defined by `PEP1 `_): @@ -56,4 +56,4 @@ Submitting a PEP Here's an overview of the PEP acceptance workflow: - .. image:: http://www.python.org/dev/peps/pep-0001/pep-0001-1.png \ No newline at end of file + .. image:: http://www.python.org/dev/peps/pep-0001/pep-0001-1.png diff --git a/docs/starting/installation.rst b/docs/starting/installation.rst index e7fa0bb3a..25edbcf7c 100644 --- a/docs/starting/installation.rst +++ b/docs/starting/installation.rst @@ -57,8 +57,8 @@ pypi.python.org, amongst a few other sources. It also plays well with *virtualenv* and user-enviornments. **easy_install** is considered by many to be a deprecated system, so we -will install it's replacement: **pip**. Pip allows for uninstallation -of packages, and is actively maintained, unlike setuptool's easy_install. +will install its replacement: **pip**. Pip allows for uninstallation +of packages and is actively maintained, unlike setuptool's easy_install. To install *pip* and Distribute's *easy_install*: diff --git a/docs/starting/which-python.rst b/docs/starting/which-python.rst index 862647a26..cbc90e563 100644 --- a/docs/starting/which-python.rst +++ b/docs/starting/which-python.rst @@ -16,7 +16,7 @@ Which Python to use? Today ----- -If you're choosing a Python interpreter to use, I *highly* recommend you Use Python 2.7.x, unless you have a strong reason not to. +If you're choosing a Python interpreter to use, I *highly* recommend you use Python 2.7.x, unless you have a strong reason not to. The Future @@ -30,4 +30,4 @@ Which Python to Support? ~~~~~~~~~~~~~~~~~~~~~~~~ If you're starting work on a new Python module, I recommend you write it for -Python 2.5 or 2.6, and add support for Python3 in a later iteration. \ No newline at end of file +Python 2.5 or 2.6, and add support for Python3 in a later iteration.