Eliminate extraneous whitespace

10 files changed, 27 insertions, 27 deletions

diff --git a/docs/contribute.rst b/docs/contribute.rst
index 82419f17..0820d5c3 100644
--- a/docs/contribute.rst
+++ b/docs/contribute.rst
@@ -23,7 +23,7 @@ different projects.
 
 To create a virtual environment, use the following syntax::
 
-    $ mkvirtualenv pelican 
+    $ mkvirtualenv pelican
 
 To clone the Pelican source::
 
@@ -65,5 +65,5 @@ Try to respect what is described in the `PEP8 specification
 <http://www.python.org/dev/peps/pep-0008/>`_ when providing patches. This can be
 eased via the `pep8 <http://pypi.python.org/pypi/pep8>`_ or `flake8
 <http://pypi.python.org/pypi/flake8/>`_ tools, the latter of which in
-particular will give you some useful hints about ways in which the 
+particular will give you some useful hints about ways in which the
 code/formatting can be improved.
diff --git a/docs/faq.rst b/docs/faq.rst
index c5c751e6..e76bea6a 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -26,7 +26,7 @@ suggestions or problems you might have via IRC or the issue tracker.
 If you want to contribute, please fork `the git repository
 <https://github.com/getpelican/pelican/>`_, create a new feature branch, make
 your changes, and issue a pull request. Someone will review your changes as soon
-as possible. Please refer to the :doc:`How to Contribute <contribute>` section 
+as possible. Please refer to the :doc:`How to Contribute <contribute>` section
 for more details.
 
 You can also contribute by creating themes and improving the documentation.
@@ -43,7 +43,7 @@ I'm creating my own theme. How do I use Pygments for syntax highlighting?
 
 Pygments adds some classes to the generated content. These classes are used by
 themes to style code syntax highlighting via CSS. Specifically, you can
-customize the appearance of your syntax highlighting via the ``.codehilite pre`` 
+customize the appearance of your syntax highlighting via the ``.codehilite pre``
 class in your theme's CSS file. To see how various styles can be used to render
 Django code, for example, you can use the demo `on the project website
 <http://pygments.org/demo/15101/>`_.
@@ -105,7 +105,7 @@ I'm getting a warning about feeds generated without SITEURL being set properly
 In order to properly generate all URLs properly in Pelican you will need to set
 ``SITEURL`` to the full path of your blog. When using ``make html`` and the
 default Makefile provided by the `pelican-quickstart` bootstrap script to test
-build your site, it's normal to see this warning since ``SITEURL`` is 
+build your site, it's normal to see this warning since ``SITEURL`` is
 deliberately left undefined. If configured properly no other ``make`` commands
 should result in this warning.
 
@@ -124,5 +124,5 @@ setting names). Here is an exact list of the renamed setting names::
 
 Older 2.x themes that referenced the old setting names may not link properly.
 In order to rectify this, please update your theme for compatibility with 3.0+
-by changing the relevant values in your template files. For an example of 
+by changing the relevant values in your template files. For an example of
 complete feed headers and usage please check out the ``simple`` theme.
diff --git a/docs/importer.rst b/docs/importer.rst
index ccf3ffe2..ba96d9c2 100644
--- a/docs/importer.rst
+++ b/docs/importer.rst
@@ -31,7 +31,7 @@ BeatifulSoup can be installed like any other Python package::
 
     $ pip install BeautifulSoup
 
-For pandoc, install a package for your operating system from the 
+For pandoc, install a package for your operating system from the
 `pandoc site <http://johnmacfarlane.net/pandoc/installing.html>`_.
 
 
diff --git a/docs/index.rst b/docs/index.rst
index 477b4342..3fc1cf9f 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -3,7 +3,7 @@ Pelican
 
 Pelican is a static site generator, written in Python_.
 
-* Write your weblog entries directly with your editor of choice (vim!) 
+* Write your weblog entries directly with your editor of choice (vim!)
   in reStructuredText_ or Markdown_
 * Includes a simple CLI tool to (re)generate the weblog
 * Easy to interface with DVCSes and web hooks
@@ -79,4 +79,4 @@ A French version of the documentation is available at :doc:`fr/index`.
 .. _`Pelican documentation`: http://docs.getpelican.com/latest/
 .. _`Pelican's internals`: http://docs.getpelican.com/en/latest/internals.html
 .. _`#pelican on Freenode`: irc://irc.freenode.net/pelican
-.. _webchat: http://webchat.freenode.net/?channels=pelican&uio=d4
\ No newline at end of file
+.. _webchat: http://webchat.freenode.net/?channels=pelican&uio=d4
diff --git a/docs/internals.rst b/docs/internals.rst
index 6b6f991f..a6264476 100644
--- a/docs/internals.rst
+++ b/docs/internals.rst
@@ -52,7 +52,7 @@ Take a look at the Markdown reader::
             text = open(filename)
             md = Markdown(extensions = ['meta', 'codehilite'])
             content = md.convert(text)
-            
+
             metadata = {}
             for name, value in md.Meta.items():
                 if name in _METADATA_FIELDS:
@@ -81,7 +81,7 @@ both; only the existing ones will be called.
   context is shared between all generators, and will be passed to the
   templates. For instance, the ``PageGenerator`` ``generate_context`` method
   finds all the pages, transforms them into objects, and populates the context
-  with them. Be careful *not* to output anything using this context at this 
+  with them. Be careful *not* to output anything using this context at this
   stage, as it is likely to change by the effect of other generators.
 
 * ``generate_output`` is then called. And guess what is it made for? Oh,
diff --git a/docs/pelican-themes.rst b/docs/pelican-themes.rst
index a074a0a2..23be8355 100644
--- a/docs/pelican-themes.rst
+++ b/docs/pelican-themes.rst
@@ -64,7 +64,7 @@ In this example, we can see there are three themes available: ``notmyidea``, ``s
 Note that you can combine the ``--list`` option with the ``-v`` or ``--verbose`` option to get more verbose output, like this:
 
 .. code-block:: console
-    
+
     $ pelican-themes -v -l
     /usr/local/lib/python2.6/dist-packages/pelican-2.6.0-py2.6.egg/pelican/themes/notmyidea
     /usr/local/lib/python2.6/dist-packages/pelican-2.6.0-py2.6.egg/pelican/themes/two-column (symbolic link to `/home/skami/Dev/Python/pelican-themes/two-column')
@@ -118,7 +118,7 @@ Creating symbolic links
 To symbolically link a theme, you can use the ``-s`` or ``--symlink``, which works exactly as the ``--install`` option:
 
 .. code-block:: console
-    
+
     # pelican-themes --symlink ~/Dev/Python/pelican-themes/two-column
 
 In this example, the ``two-column`` theme is now symbolically linked to the Pelican themes path, so we can use it, but we can also modify it without having to reinstall it after each modification.
@@ -130,11 +130,11 @@ This is useful for theme development:
     $ sudo pelican-themes -s ~/Dev/Python/pelican-themes/two-column
     $ pelican ~/Blog/content -o /tmp/out -t two-column
     $ firefox /tmp/out/index.html
-    $ vim ~/Dev/Pelican/pelican-themes/two-coumn/static/css/main.css 
+    $ vim ~/Dev/Pelican/pelican-themes/two-coumn/static/css/main.css
     $ pelican ~/Blog/content -o /tmp/out -t two-column
     $ cp /tmp/bg.png ~/Dev/Pelican/pelican-themes/two-coumn/static/img/bg.png
     $ pelican ~/Blog/content -o /tmp/out -t two-column
-    $ vim ~/Dev/Pelican/pelican-themes/two-coumn/templates/index.html 
+    $ vim ~/Dev/Pelican/pelican-themes/two-coumn/templates/index.html
     $ pelican ~/Blog/content -o /tmp/out -t two-column
 
 
@@ -152,7 +152,7 @@ The ``--install``, ``--remove`` and ``--symlink`` option are not mutually exclus
                      --symlink ~/Dev/Python/pelican-themes/two-column \
                      --verbose
 
-In this example, the theme ``notmyidea-cms`` is replaced by the theme ``notmyidea-cms-fr`` 
+In this example, the theme ``notmyidea-cms`` is replaced by the theme ``notmyidea-cms-fr``
 
 
 
diff --git a/docs/plugins.rst b/docs/plugins.rst
index 99c0429a..7743c552 100644
--- a/docs/plugins.rst
+++ b/docs/plugins.rst
@@ -16,7 +16,7 @@ To load plugins, you have to specify them in your settings file. You have two
 ways to do so.
 Either by specifying strings with the path to the callables::
 
-    PLUGINS = ['pelican.plugins.gravatar',] 
+    PLUGINS = ['pelican.plugins.gravatar',]
 
 Or by importing them and adding them to the list::
 
diff --git a/docs/report.rst b/docs/report.rst
index f12f3048..f3ddff31 100644
--- a/docs/report.rst
+++ b/docs/report.rst
@@ -4,7 +4,7 @@ Some history about Pelican
 .. warning::
 
     This page comes from a report the original author (Alexis Métaireau) wrote
-    right after writing Pelican, in December 2010. The information may not be 
+    right after writing Pelican, in December 2010. The information may not be
     up-to-date.
 
 Pelican is a simple static blog generator. It parses markup files
@@ -113,7 +113,7 @@ concepts. Here is what happens when calling the ``generate_context``
 method:
 
 * Read the folder “path”, looking for restructured text files, load
-  each of them, and construct a content object (``Article``) with it. To do so, 
+  each of them, and construct a content object (``Article``) with it. To do so,
   use ``Reader`` objects.
 * Update the ``context`` with all those articles.
 
diff --git a/docs/themes.rst b/docs/themes.rst
index d3dd4d9e..7598a28c 100644
--- a/docs/themes.rst
+++ b/docs/themes.rst
@@ -35,7 +35,7 @@ To make your own theme, you must follow the following structure::
 * `templates` contains all the templates that will be used to generate the content.
   I've just put the mandatory templates here; you can define your own if it helps
   you keep things organized while creating your theme.
- 
+
 Templates and variables
 =======================
 
@@ -44,7 +44,7 @@ This document describes which templates should exist in a theme, and which
 variables will be passed to each template at generation time.
 
 All templates will receive the variables defined in your settings file, if they
-are in all-caps. You can access them directly. 
+are in all-caps. You can access them directly.
 
 Common variables
 ----------------
@@ -55,14 +55,14 @@ All of these settings will be available to all templates.
 Variable        Description
 =============   ===================================================
 articles        The list of articles, ordered descending by date
-                All the elements are `Article` objects, so you can 
+                All the elements are `Article` objects, so you can
                 access their attributes (e.g. title, summary, author
                 etc.)
 dates           The same list of articles, but ordered by date,
                 ascending
 tags            A key-value dict containing the tags (the keys) and
                 the list of respective articles (the values)
-categories      A key-value dict containing the categories (keys) 
+categories      A key-value dict containing the categories (keys)
                 and the list of respective articles (values)
 pages           The list of pages
 =============   ===================================================
@@ -182,7 +182,7 @@ dates                   Articles related to this tag, but ordered by date,
                         ascending
 articles_paginator      A paginator object for the list of articles
 articles_page           The current page of articles
-dates_paginator         A paginator object for the list of articles, 
+dates_paginator         A paginator object for the list of articles,
                         ordered by date, ascending
 dates_page              The current page of articles, ordered by date,
                         ascending
diff --git a/docs/tips.rst b/docs/tips.rst
index 8905103b..abb739b1 100644
--- a/docs/tips.rst
+++ b/docs/tips.rst
@@ -12,11 +12,11 @@ file generator, we can take advantage of this.
 
 User Pages
 ----------
-GitHub allows you to create user pages in the form of ``username.github.com``. 
+GitHub allows you to create user pages in the form of ``username.github.com``.
 Whatever is created in the master branch will be published. For this purpose,
 just the output generated by Pelican needs to pushed to GitHub.
 
-So given a repository containing your articles, just run Pelican over the posts 
+So given a repository containing your articles, just run Pelican over the posts
 and deploy the master branch to GitHub::
 
     $ pelican -s pelican.conf.py ./path/to/posts -o /path/to/output
@@ -35,7 +35,7 @@ really easy, which can be installed via::
 
     $ pip install ghp-import
 
-Then, given a repository containing your articles, you would simply run 
+Then, given a repository containing your articles, you would simply run
 Pelican and upload the output to GitHub::
 
     $ pelican -s pelican.conf.py .