summaryrefslogtreecommitdiff
path: root/docs/tutorials/wiki
diff options
context:
space:
mode:
authorkenmanheimer <ken.manheimer@gmail.com>2011-11-08 14:26:43 -0800
committerkenmanheimer <ken.manheimer@gmail.com>2011-11-08 14:26:43 -0800
commit42410ef646d4427adc3f5d8a5d11b48fd51c0a08 (patch)
treed06fc2142fb2e273d57a12264399c3383ced0244 /docs/tutorials/wiki
parentf846512f9946810f978f8df1e37e602fbee948bd (diff)
downloadpyramid-42410ef646d4427adc3f5d8a5d11b48fd51c0a08.tar.gz
pyramid-42410ef646d4427adc3f5d8a5d11b48fd51c0a08.tar.bz2
pyramid-42410ef646d4427adc3f5d8a5d11b48fd51c0a08.zip
Use active ("Run the Tests") rather than passive ("Running the Tests")
voice for the headings.
Diffstat (limited to 'docs/tutorials/wiki')
-rw-r--r--docs/tutorials/wiki/installation.rst20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/tutorials/wiki/installation.rst b/docs/tutorials/wiki/installation.rst
index 0509f4e44..4153b9dfd 100644
--- a/docs/tutorials/wiki/installation.rst
+++ b/docs/tutorials/wiki/installation.rst
@@ -127,8 +127,8 @@ Preparation, Windows
.. _making_a_project:
-Making a Project
-================
+Make a Project
+==============
Your next step is to create a project. :app:`Pyramid` supplies a variety of
scaffolds to generate sample projects. For this tutorial, we will use the
@@ -159,8 +159,8 @@ On Windows:
problems, try putting both the virtualenv and the project into
directories that do not contain spaces in their paths.
-Installing the Project in "Development Mode"
-============================================
+Install the Project in "Development Mode"
+=========================================
In order to do development on the project easily, you must "register"
the project as a development egg in your workspace using the
@@ -184,8 +184,8 @@ On Windows:
.. _running_tests:
-Running the Tests
-=================
+Run the Tests
+=============
After you've installed the project in development mode, you may run
the tests for the project.
@@ -202,8 +202,8 @@ On Windows:
c:\pyramidtut\tutorial> ..\Scripts\python setup.py test -q
-Exposing Test Coverage Information
-==================================
+Expose Test Coverage Information
+================================
You can run the ``nosetests`` command to see test coverage
information. This runs the tests in the same way that ``setup.py
@@ -228,8 +228,8 @@ Looks like the code in the ``pyramid_zodb`` scaffold for ZODB projects is
missing some test coverage, particularly in the file named
``models.py``.
-Starting the Application
-========================
+Start the Application
+=====================
Start the application.