quick_tutorial/tutorial_approach - Fix up the process description to reflect reality

1 files changed, 5 insertions, 6 deletions

diff --git a/docs/quick_tutorial/tutorial_approach.rst b/docs/quick_tutorial/tutorial_approach.rst
index 49a6bfd85..d944aaebd 100644
--- a/docs/quick_tutorial/tutorial_approach.rst
+++ b/docs/quick_tutorial/tutorial_approach.rst
@@ -10,18 +10,17 @@ Details, references, and deeper discussions are mentioned in "See also" notes.
 This "Getting Started" tutorial is broken into independent steps, starting with
 the smallest possible "single file WSGI app" example. Each of these steps
 introduce a topic and a very small set of concepts via working code. The steps
-each correspond to a directory in this repo, where each step/topic/directory is
+each correspond to a directory in this repository, where each step's directory is
 a Python package.
 
-To successfully run each step:
+To successfully run each step, you'll usually copy the current step's directory to a new directory, change your working directory to the new directory, then install your project:
 
 .. code-block:: bash
 
-    $ cd request_response
+    $ cd ..; cp -r package ini; cd ini
     $ $VENV/bin/pip install -e .
 
-...and repeat for each step you would like to work on. In most cases we will
-start with the results of an earlier step.
+For a few steps, you won't copy the step's directory.
 
 Directory tree
 ==============
@@ -43,5 +42,5 @@ below:
 
 Each of the first-level directories (e.g., ``request_response``) is a *Python
 project* (except as noted for the ``hello_world`` step). The ``tutorial``
-directory is a *Python package*. At the end of each step, we copy a previous
+directory is a *Python package*. At the start of each step, we usually copy a previous
 directory into a new directory to use as a starting point.