improve wording regarding pyvenv

1 files changed, 9 insertions, 8 deletions

diff --git a/docs/narr/install.rst b/docs/narr/install.rst
index 882e76f11..8a8513348 100644
--- a/docs/narr/install.rst
+++ b/docs/narr/install.rst
@@ -245,18 +245,19 @@ your setuptools-enabled Python interpreter, use the ``easy_install`` command.
 
 .. warning::
 
-   Even though Python 3.3 and better comes with ``pyvenv`` out of the box,
-   which is similar to ``virtualenv``, we suggest using ``virtualenv`` instead.
-   ``virtualenv`` works on well Python 3.3.  This isn't a recommendation made
-   for technical reasons, it's one made because it's not feasible for the
+   Python 3.3 includes ``pyvenv`` out of the box, which provides similar
+   functionality to ``virtualenv``.
+   We however suggest using ``virtualenv`` instead,
+   which works well with Python 3.3.
+   This isn't a recommendation made for technical reasons;
+   it's made because it's not feasible for the
    authors of this guide to explain setup using multiple virtual environment
    systems.  We are aiming to not need to make the installation documentation
    Turing-complete.
 
-   ``pyvenv`` will work fine.  However, if you use ``pyvenv`` instead of
-   ``virtualenv``, you'll need to understand how to install software such as
-   ``distribute`` into the virtual environment manually, which this guide does
-   not cover.
+   If you insist on using ``pyvenv``, you'll need to understand how to install
+   software such as``distribute`` into the virtual environment manually,
+   which this guide does not cover.
 
 .. code-block:: text