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: These directions, and the ordering of tasks, are only suggestions unless
  otherwise noted.
  
  ## <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> Job VMs and Compilation VMs ###
  
  When you deploy a release, BOSH creates two kinds of VMs on the target IaaS:
  
  
negative.code: When creating dev releases, do not run `bosh upload blobs`.
  (You only run it when you do a final release.)
  
  ## <a id="create-props"></a> Step 5: Create Job Properties  ##
  
  If your service needs to be configurable at deployment time,
  you create the desired inputs or controls and specify them in the release.
  