From 9065ff56233cbd1be312b116ea94a7a474a61361 Mon Sep 17 00:00:00 2001
From: Doug Hellmann <doug.hellmann@dreamhost.com>
Date: Wed, 5 Jun 2013 18:48:40 -0400
Subject: [PATCH] doc cleanup

Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
---
 docs/source/history.rst          |  1 +
 docs/source/tutorial/loading.rst | 13 ++++++-------
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/source/history.rst b/docs/source/history.rst
index f2481f3..408580f 100644
--- a/docs/source/history.rst
+++ b/docs/source/history.rst
@@ -15,6 +15,7 @@ dev
 - Add ``__getitem__`` to
   :class:`~stevedore.extension.ExtensionManager` for looking up
   individual plugins by name (:issue:`15`).
+- Start working on the tutorial, :doc:`tutorial/index`.
 
 0.8
 
diff --git a/docs/source/tutorial/loading.rst b/docs/source/tutorial/loading.rst
index d07687a..d9e04c4 100644
--- a/docs/source/tutorial/loading.rst
+++ b/docs/source/tutorial/loading.rst
@@ -2,17 +2,16 @@
  Loading the Plugins
 =====================
 
-Load plugins using stevedore is as easy as creating them. There are
-several different enabling and invocation patterns to choose from,
-depending on your needs.
+There are several different enabling and invocation patterns for
+consumers of plugins, depending on your needs.
 
 Loading Drivers
 ===============
 
-The most common way plugins are used is as individual drivers. There
-may be many plugin options to choose from, but only one needs to be
-loaded and called. The :class:`~stevedore.driver.DriverManager` class
-supports this pattern.
+The most common way plugins are used is as individual drivers. In this
+case, there may be many plugin options to choose from, but only one
+needs to be loaded and called. The
+:class:`~stevedore.driver.DriverManager` class supports this pattern.
 
 This example program uses a :class:`DriverManager` to load a formatter
 defined in the examples for stevedore. It then uses the formatter to