Tweak docs

Author: edschofield

README.rst

@@ -1,21 +1,21 @@
 .. _overview:
 
-Overview: an easier, safer, cleaner upgrade path to Python 3
-============================================================
+Overview: Easy, clean, reliable Python 2/3 compatibility
+========================================================
 
-
-``python-future`` is the missing compatibility layer between Python 3 and
-Python 2. It allows you to maintain a single, clean Python 3.x-compatible
-codebase with minimal cruft and run it easily on Python 2 mostly unchanged.
+``python-future`` is the missing compatibility layer between Python 2 and
+Python 3. It allows you to use a single, clean Python 3.x-compatible
+codebase to support both Python 2 and Python 3 with minimal overhead.
 
 It provides ``future`` and ``past`` packages with backports and forward ports of
 features from Python 3 and 2. It also comes with ``futurize`` and
 ``pasteurize``, customized 2to3-based scripts that helps you to convert either
 Py2 or Py3 code easily to support both Python 2 and 3 in a single clean
 Py3-style codebase, module by module.
 
-Notable projects that use ``future`` for Python 3/2 compatibility are `Mezzanine
-<http://mezzanine.jupo.org/>`_ and `ObsPy <http://obspy.org>`_.
+Notable projects that use ``python-future`` for Python 3/2 compatibility
+are `Mezzanine <http://mezzanine.jupo.org/>`_ and `ObsPy
+<http://obspy.org>`_.
 
 .. _features:
 
@@ -254,14 +254,15 @@ Licensing
 ---------
 
 :Author:  Ed Schofield
+
+:Copyright: 2013-2014 Python Charmers Pty Ltd, Australia.
+
 :Sponsor: Python Charmers Pty Ltd, Australia, and Python Charmers Pte
           Ltd, Singapore. http://pythoncharmers.com
-:Others:  See `Credits <http://python-future.org/credits.html>`_.
 
-Copyright 2013-2014 Python Charmers Pty Ltd, Australia.
+:Licence: MIT. See ``LICENSE.txt`` or `here <http://python-future.org/credits.html>`_.
 
-The software is distributed under an MIT licence. See ``LICENSE.txt`` or `Licensing
-<http://python-future.org/licensing.html>`_.
+:Other credits:  See `here <http://python-future.org/credits.html>`_.
 
 
 Next steps

docs/_templates/sidebarintro.html

@@ -1,6 +1,6 @@
 <!--<h3>Python-Future</h3>
 <p>-->
-  <h4>An easier, safer, cleaner upgrade path to Python 3.</h4>
+  <h4>Easy, clean, reliable Python 2/3 compatibility</h4>
 <!--
 </p>
 <h3>Other Formats</h3>
@@ -14,6 +14,6 @@ <h3>Other Formats</h3>
 -->
 <!--<h3>Useful Links</h3>-->
 <ul>
-  <li><a href="http://pypi.python.org/pypi/future">future @ PyPI</a></li>
-  <li><a href="https://github.com/PythonCharmers/python-future">future @ github</a></li>
+  <li><a href="http://pypi.python.org/pypi/future">on PyPI</a></li>
+  <li><a href="https://github.com/PythonCharmers/python-future">on GitHub</a></li>
 </ul>

docs/faq.rst

@@ -207,8 +207,9 @@ What is the relationship between ``future`` and ``six``?
 --------------------------------------------------------
 
 ``python-future`` is a higher-level compatibility layer than ``six`` that
-includes more backported functionality from Python 3 and supports cleaner
-code but requires more modern Python versions to run.
+includes more backported functionality from Python 3, more forward-ported
+functionality from Python 2, and supports cleaner code, but requires more
+modern Python versions to run.
 
 ``python-future`` and ``six`` share the same goal of making it possible to write
 a single-source codebase that works on both Python 2 and Python 3.

docs/index.rst

@@ -1,8 +1,8 @@
-future: clean single-source support for Python 2/3
-======================================================
+Easy, clean, reliable Python 2/3 compatibility
+==============================================
 
-``future`` is the missing compatibility layer between Python 2 and Python
-3. It allows you to use a single, clean Python 3.x-compatible
+``python-future`` is the missing compatibility layer between Python 2 and
+Python 3. It allows you to use a single, clean Python 3.x-compatible
 codebase to support both Python 2 and Python 3 with minimal overhead.