give installation a colectomy; give it headings;

1 files changed, 40 insertions, 20 deletions

diff --git a/docs/tutorials/wiki2/installation.rst b/docs/tutorials/wiki2/installation.rst
index 3543d9b9c..17788cdde 100644
--- a/docs/tutorials/wiki2/installation.rst
+++ b/docs/tutorials/wiki2/installation.rst
@@ -20,7 +20,8 @@ Next let's create a `virtualenv` workspace for our project.  We will
 use the `VENV` environment variable instead of absolute path of the
 virtual environment.
 
-**On UNIX:**
+On UNIX
+^^^^^^^
 
 .. code-block:: text
 
@@ -29,7 +30,8 @@ virtual environment.
    New python executable in /home/foo/env/bin/python
    Installing setuptools.............done.
 
-**On Windows:**
+On Windows
+^^^^^^^^^^
 
 Set the `VENV` environment variable.
 
@@ -55,13 +57,15 @@ Python 3.2:
 Install Pyramid Into the Virtual Python Environment
 ---------------------------------------------------
 
-**On UNIX:**
+On UNIX
+^^^^^^^
 
 .. code-block:: text
 
    $ $VENV/bin/easy_install pyramid
 
-**On Windows:**
+On Windows
+^^^^^^^^^^
 
 .. code-block:: text
 
@@ -88,13 +92,15 @@ Change Directory to Your Virtual Python Environment
 
 Change directory to the ``pyramidtut`` directory.
 
-**On UNIX:**
+On UNIX
+^^^^^^^
 
 .. code-block:: text
 
    $ cd pyramidtut
 
-**On Windows:**
+On Windows
+^^^^^^^^^^
 
 .. code-block:: text
 
@@ -123,13 +129,15 @@ required files. For example, `pcreate` creates the
 The below instructions assume your current working directory is the
 "virtualenv" named "pyramidtut".
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/pcreate -s alchemy tutorial
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -152,14 +160,16 @@ the project as a development egg in your workspace using the
 directory you created in :ref:`sql_making_a_project`, and run the
 ``setup.py develop`` command using the virtualenv Python interpreter.
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ cd tutorial
    $ $VENV/bin/python setup.py develop
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -180,13 +190,15 @@ Running the Tests
 After you've installed the project in development mode, you may run
 the tests for the project.
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/python setup.py test -q
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -212,13 +224,15 @@ tests.
 To get this functionality working, we'll need to install the ``nose`` and
 ``coverage`` packages into our ``virtualenv``:
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/easy_install nose coverage
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -227,13 +241,15 @@ To get this functionality working, we'll need to install the ``nose`` and
 Once ``nose`` and ``coverage`` are installed, we can actually run the
 coverage tests.
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/nosetests --cover-package=tutorial --cover-erase --with-coverage
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -271,13 +287,15 @@ script` to initialize our database.
 Type the following command, make sure you are still in the ``tutorial``
 directory (the directory with a ``development.ini`` in it):
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/initialize_tutorial_db development.ini
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text
 
@@ -319,13 +337,15 @@ Starting the Application
 
 Start the application.
 
-**On UNIX:**
+On UNIX
+-------
 
 .. code-block:: text
 
    $ $VENV/bin/pserve development.ini --reload
 
-**On Windows:**
+On Windows
+----------
 
 .. code-block:: text