anchor.diff:  This section needs to be completed once.
   Next, you iterate through Steps 1 through 6 until your dev release is
   satisfactory.
  -Then you do a final release.
  +Then you can do a final release.
   
   ### <a id="release-dir"></a>Create the release directory ###
  -
  -All parts of a release reside in the _release directory_.
   
   To create the release directory, navigate into the workspace where you want the
   release to be, and run:
   
     `bosh init release <release_name>`
   
  -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.
  -
  -In the release directory, BOSH creates a subdirectory for each of the
  -fundamental elements: jobs, packages, source (which BOSH calls `src`), and
  -blobs.
  -
  -### <a id="directory-structure"></a> About directory structure on job VMs ###
  +Use dashes in the release name.
  +Use underscores for all other filenames in the release.
   
   View the release with `tree`:
   
  
positive.code: 
  ### <a id="build-graph"> </a>Building the Dependency Graph ###
  
  Creating a dependency graph helps clarify your understanding of the
  dependencies between the jobs and packages in your release, and provides a
  reference as you add elements to the release.
  
  As you build the dependency graph, you discover dependencies on packages
  and record them in the graph.
  When the time comes to add packages to your release, the dependency graph
  is your guide.
  
  #### <a id="runtime"> </a>Identify runtime dependencies ####
  
  
negative.code: 
  ### <a id="source"></a> Populate the src directory ###
  
  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 ###
  
  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.
  
  ## <a id="job-skel"></a> Step 1: Create Job Skeletons ##
  
  Navigate into the release directory.
  
  For each job, create a job skeleton:
  
    `bosh generate job <job_name>`
  
  