From d0aa7c820b8e654bdf23382a08ba26d3e58a0a4b Mon Sep 17 00:00:00 2001
From: Adrian Holovaty <adrian@holovaty.com>
Date: Mon, 17 Mar 2008 16:56:05 +0000
Subject: [PATCH] Fixed the inevitable ReST errors in docs/form_wizard.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@7266 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/form_wizard.txt | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/form_wizard.txt b/docs/form_wizard.txt
index b7144ebef2..51b09ca132 100644
--- a/docs/form_wizard.txt
+++ b/docs/form_wizard.txt
@@ -41,15 +41,15 @@ Usage
 This application handles as much machinery for you as possible. Generally, you
 just have to do these things:
 
-    # Define a number of ``django.newforms`` ``Form`` classes -- one per wizard
-      page.
-    # Create a ``FormWizard`` class that specifies what to do once all of your
-      forms have been submitted and validated. This also lets you override some
-      of the wizard's behavior.
-    # Create some templates that render the forms. You can define a single,
-      generic template to handle every one of the forms, or you can define a
-      specific template for each form.
-    # Point your URLconf at your ``FormWizard`` class.
+    1. Define a number of ``django.newforms`` ``Form`` classes -- one per wizard
+       page.
+    2. Create a ``FormWizard`` class that specifies what to do once all of your
+       forms have been submitted and validated. This also lets you override some
+       of the wizard's behavior.
+    3. Create some templates that render the forms. You can define a single,
+       generic template to handle every one of the forms, or you can define a
+       specific template for each form.
+    4. Point your URLconf at your ``FormWizard`` class.
 
 Defining ``Form`` classes
 =========================
@@ -97,7 +97,7 @@ and validated. This method is passed two arguments:
     * ``form_list`` -- a list of ``django.newforms`` ``Form`` classes
 
 In this simplistic example, rather than perform any database operation, the
-method simply  renders a template of the validated data::
+method simply renders a template of the validated data::
 
     from django.shortcuts import render_to_response
     from django.contrib.formtools.wizard import FormWizard
@@ -134,7 +134,7 @@ change this template name by overriding ``FormWizard.get_template()``, which is
 documented below. This hook also allows you to use a different template for
 each form.)
 
-This template expects the following context::
+This template expects the following context:
 
     * ``step_field`` -- The name of the hidden field containing the step.
     * ``step0`` -- The current step (zero-based).