Make "make check" happy.

doc/config.rst

@@ -160,7 +160,7 @@ General configuration
       """
 
    .. versionadded:: 0.6
-   
+
 .. confval:: default_role
 
    .. index:: default; role
@@ -302,7 +302,7 @@ Project information
 
    .. versionadded:: 0.6
 
-   
+
 .. _html-options:
 
 Options for HTML output

doc/faq.rst

@@ -17,7 +17,7 @@ How do I...
 
 ... write my own extension?
    See the :ref:`extension tutorial <exttut>`.
-   
+
 ... use Sphinx with Epydoc?
    There's a third-party extension providing an `api role`_ which refers to
    Epydoc's API docs for a given identifier.

doc/templating.rst

@@ -342,7 +342,7 @@ in the future.
 In addition to these values, there are also all **theme options** available
 (prefixed by ``theme_``), as well as the values given by the user in
 :confval:`html_context`.
-   
+
 In documents that are created from source files (as opposed to
 automatically-generated files like the module index, or documents that already
 are in HTML form), these variables are also available:

doc/theming.rst

@@ -178,7 +178,7 @@ templating to put the color options into the stylesheet.  When a documentation
 is built with the default theme, the output directory will contain a
 ``_static/default.css`` file where all template tags have been processed.
 
-  
+
 .. [1] It is not an executable Python file, as opposed to :file:`conf.py`,
        because that would pose an unnecessary security risk if themes are
        shared.