anchor.diff:  
   The `monit` file:
   
  -* Specifies the process ID (pid) file for the job.
  -* References each command provided by the templates for the job.
  -* Specifies that the job belongs to the `vcap` group.
  +* Specifies the process ID (pid) file for the job
  +* References each command provided by the templates for the job
  +* Specifies that the job belongs to the `vcap` group
   
   On a deployed release, a BOSH Agent runs on each job VM.
  -BOSH communicates with the Agent, which in turn executes the commands you have
  -provided in the control script.
  -The Agent does this with the help of [Monit](http://mmonit.com/monit/),
  +BOSH communicates with the Agent, which in turn executes commands in the
  +control script.
  +The Agent does this using [Monit](http://mmonit.com/monit/),
   which is open source software for monitoring processes, programs, files, and
   directories.
   
  
positive.code: 
  Because the environments of compilation VMs and job VMs are identical,
  BOSH frees you from concerns about discrepancies between compilation
  environment and deployment environment.
  
  Compilation VMs never contain software left over from previous
  deployments, because they are newly created when you deploy, and destroyed
  once compilation is done.
  Job VMs are newly created and cannot contain software left over from previous
  deployments in two cases: the first time you deploy a release, and every time
  that you deploy using the `--recreate` option.
  By compiling and deploying on fresh VMs, BOSH assures that your VMs are in a
  known state in terms of what software is present.
  
  ## <a id="release-dir"></a> Create the Release Directory ##
  
  All the constituent parts of a release reside in the _release directory_.
  
  `cd` into the workspace where you want the release to be, and create the release directory:
  
    `bosh init release <release_name> --git`
  
  The `--git` option initializes a git repo in the release directory.
  This is recommended but not required.
  
  Our example release is named `ardo-release`.
  The name "ardo" was chosen arbitrarily, but the dash was not.
  The release name should have dashes rather than underscores, to conform to the
  convention for Git repo names.
  All other filenames in the release should use underscores.
  
  `cd` into the release directory.
  This is where all the BOSH commands in this tutorial are run from here on.
  
  ### <a id="directory-structure"></a> Directory structure on job VMs ###
  
  
negative.code: 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.
  
  Navigate into the release directory.
  From here on, this tutorial assumes that you run all commands from there.
  
  ## <a id="job-skel"></a> 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:
  
    `bosh generate job <job_name>`
  
  