anchor.diff:  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 ##
  +## <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.
  
positive.code: For a large or complicated release, you might prefer to make more than one
  dependency graph.
  
  ## <a id="pkg-skeletons"></a> Create Package Skeletons ##
  
  Packages give BOSH the information needed to prepare the binaries and
  dependencies for your jobs.
  
negative.code: * Job VMs are newly created in two cases: the first time you deploy a release,
  and every time that you deploy using the `--recreate` option.
  
  ### <a id="what"></a> Decide What to Release ###
  
  A BOSH release contains one or more pieces of software that work together.
  For example, you could create a BOSH release of a service with three pieces:
  two MySQL nodes and a dashboard app.
  You may think of these pieces as areas of functionality, or features, or roles.
  In a BOSH release, you make each piece a _job_.
  
  Jobs are among the four fundamental elements in a BOSH release.
  The others each provide something another element needs:
  
  * **Jobs** describe pieces of the service or application you are releasing
  * **Packages** provide source code and dependencies to jobs
  * **Source** provides packages the non-binary files they need
  * **Blobs** provide packages the binaries they need, other than binaries that
  are checked into a source code repository
  
  You make judgment calls when creating a release:
  what to include, how to structure it, and how to split up jobs and packages.
  To get started creating a release, decide what jobs your release should include.
  
  Our example release includes two jobs: a web UI and a background worker.
  The worker periodically sends an HTTP request to the web UI, and the web UI
  displays the number of worker requests received.
  The two jobs split up the functionality provided by single Ruby app,
  `ardo_app`.
  
  You also decide what properties to give your jobs.
  Job properties are essentially inputs.
  In our example, we have decided to create one property:
  the port on which the web UI listens.
  
  ### <a id="release-dir"></a> Create the release directory ###
  
  All parts of the release reside in the _release directory_.
  
  