anchor.diff:  
   ### <a id="source"></a> Populate the src directory ###
   
  -Populate the `src` directory with your source code.
  -
  -For this tutorial, copy your code directory into `src`.
  -
  -For production, consider using a Git [submodule]
  -(https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial), Mercurial
  -repository, or other mechanism to ensure that users of your release
  -always access the correct versions of dependencies even when those versions
  -are no longer current.
  -This is important for large BOSH releases. For example, [Cloud Foundry]
  -(https://github.com/cloudfoundry/cf-release) has more than thirty Git submodules.
  +Copy your source code into the `src` directory.
  +Alternatively, link your source code to the directory using a mechanism such as
  +a Git submodule or a Mercurial repo.
   
   ### <a id="strategy"></a> Choose a work strategy ###
   
  -You are about to begin five central parts of the tutorial,
  -Create Job Skeletons, Make Dependency Graphs, Create Packages, Add Blobs, and
  -Create Job Properties.
  -You can proceed in either of two ways:
  -
  -1. **One section at a time**. Complete one section for all jobs, then do the same for in the next section, and so on.
  -
  -1. **One job at a time**. Complete all four sections for one job, do the same for the next job, and so on.
  -
  -For releases with just a few jobs, going one section at a time is probably easiest.
  -We'll do that in this tutorial.
  +Choose whether you want to work one Step at a time or one job at a time.
  +For releases with just a few jobs, going one Step at a time is probably easiest.
   If you have a larger number of jobs, going one job at a time may be more efficient.
  -Choose the approach that seems most comfortable and least error-prone.
  +
  +## <a id="job-skel"></a> Step 1: Create Job Skeletons ##
   
   Navigate into the release directory.
  -From here on, this tutorial assumes that you run all commands from there.
  -
  -## <a id="job-skel"></a> Step 1: Create Job Skeletons ##
  -
  -When first created, the job is a _skeleton_: an empty structure that fills up
  -as release creation progresses.
  -
  -Run this command once for each job in your release:
  +
  +For each job, create a job skeleton:
   
     `bosh generate job <job_name>`
   
  
positive.code: 9 directories, 5 files
  </pre>
  
  Every job needs a way to start and stop.
  You provide that by writing a control script and updating the `monit` file.
  
  ### <a id="control"></a> Create control scripts  ###
  
  The control script:
  
  * Includes a start command and a stop command.
  * Is an ERb template stored in the `templates` directory for the relevant job.
  
  At compile time, BOSH transforms templates into files, which it then replicates
  on the job VMs.
  For each job, create a control script and save it as `ctl.erb` in the `templates`
   directory for its job.
  
  
negative.code: 
      <%= image_tag("dep-graph.png") %>
  
  For a large or complicated release, consider making more than one dependency
  graph.
  
  ## <a id="pkg-skeletons"></a> Step 3: Create Package Skeletons ##
  
  Packages give BOSH the information needed to prepare the binaries and
  dependencies for your jobs.
  
  Create package skeletons starting from the bottom of your dependency graph.
  
    `bosh generate package <dependency_name>`
  
  