changes to grammar and spelling done after proofreading and a nap.

deployment/gae_buildout.rst

@@ -10,13 +10,10 @@ Engine <http://code.google.com/appengine/>`_. This one uses `buildout
 to look at :ref:`appengine_tutorial`.
 
 
-Step by Step
-------------
-
 Let's take it step by step.
 
 Install the pyramid_appengine scaffold
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------------------
 
 You can get `pyramid_appengine
 <http://pypi.python.org/pypi/pyramid_appengine/>`_ from pypi via `pip <http://pypi.python.org/pypi/pip>`_
@@ -26,7 +23,7 @@ just as you typically would any other python package.
  
    $ pip install pyramid_appengine
 
-Once sucessfully installed a new project template is available to use
+Once successfully installed a new project template is available to use
 named "appengine_starter".
 
 To get a list of all available templates.
@@ -36,7 +33,7 @@ To get a list of all available templates.
    $ paster create --list-templates
 
 Create the skeleton for your project
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+------------------------------------
 
 You create your project skeleton using the "appengine_starter" project
 scaffold just as you would using any other project scaffold. 
@@ -45,14 +42,14 @@ scaffold just as you would using any other project scaffold.
 
    $ paster create -t appengine_starter newproject
 
-Once sucessfully ran, you will have new a `buildout <http://www.buildout.org>`_ directory for your project. The app engine
+Once successfully ran, you will have a new `buildout <http://www.buildout.org>`_ directory for your project. The app engine
 application source is located at newproject/src/newproject.
 
-This buildout directory can be added to version control if you like
+This buildout directory can be added to version control if you like,
 using any of the available version control tools available to you.
 
 Bootstrap the buildout
-~~~~~~~~~~~~~~~~~~~~~~
+----------------------
 
 Before you do anything with a new buildout directory you need to
 bootstrap it, which installs buildout locally and everything necessary
@@ -71,9 +68,9 @@ buildout command. See the `buildout documentation <http://www.buildout.org/docs/
 
 
 Run buildout
-~~~~~~~~~~~~
+------------
 
-As with all buildouts, after it has been bootsrapped, a "bin"
+As with all buildouts, after it has been bootstrapped, a "bin"
 directory is created with a new buildout command. This command is run
 to install things based on the newproject/buildout.cfg which you can
 edit to suit your needs.
@@ -96,7 +93,7 @@ of several things that you need to do....
 
 
 Run your tests
-~~~~~~~~~~~~~~
+--------------
 
 Your project is configured to run all tests found in files that begin with "test\_"(example: newproject/src/newproject/newproject/test_views.py).
 
@@ -110,7 +107,7 @@ Your project incorporates the `unit testing tools <http://code.google.com/appeng
 You can adjust how the app engine api's are initialized for your tests by editing newproject/src/newproject/newproject/conftest.py.
 
 Run your application locally
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+----------------------------
 You can run your application using the app engine SDK's `Development Server <http://code.google.com/appengine/docs/python/tools/devserver.html>`_
 
 .. code-block:: text
@@ -122,7 +119,7 @@ to see it working.
 
 
 Deploy to App Engine
-~~~~~~~~~~~~~~~~~~~~
+--------------------
 
 Note: Before you can upload any appengine application you must create an `application ID <http://code.google.com/appengine/docs/python/gettingstarted/uploading.html>`_ for it. 
 
@@ -132,16 +129,16 @@ To upload your application to app engine, run the following command. For more in
 
    ~/newproject/ $ ./bin/appcfg update parts/newproject -A newproject -V dev
 
-You would point your browser at `http://dev.newproject.appspot.com <http://dev.newproject.appspot.com>`_ to see it working.
+Point your browser at `http://dev.newproject.appspot.com <http://dev.newproject.appspot.com>`_ to see it working.
 
-The above command will most likely not work for you, it is just an example. the "-A" switch indicates an Application ID to deploy to, use the Application ID you created when you registered the application and overrides the setting in the app.yaml. The "-V" switch specifies the version and overrides the setting in your app.yaml. 
+The above command will most likely not work for you, it is just an
+example. the "-A" switch indicates an `Application ID <http://code.google.com/appengine/docs/python/gettingstarted/uploading.html>`_ to deploy to and overrides the setting in the app.yaml, use the Application ID you created when you registered the application instead. The "-V" switch specifies the version and overrides the setting in your app.yaml. 
 
-You can set which version of your application handles requests by default in the admin console. However you can also specify a version of your application to hit in the url like so...
+You can set which version of your application handles requests by
+default in the `admin console <http://appengine.google.com>`_. However you can also specify a version of your application to hit in the URL like so...
 
 .. code-block:: text
 
-   http://<appversion>.<application-id>.appspot.com
+   http://<app-version>.<application-id>.appspot.com
 
 This can come in pretty handy in a variety of scenarios that become obvious once you start managing the development of your application while supporting a current release. 
-
-