anchor.diff:  ### <a id="job-specs"></a> Update job specs  ###
   
   Metadata for each job resides in a `spec` file.
  -The `spec` file has a `templates` block which you must update as described
  -in this section.
  -
  -BOSH makes templates into files on VMs at compile time.
  -
  -In the `templates` block of the `spec` file for each job:
  -
  -* Each template name is a key.
  -* Each path to the corresponding file on a job VM is a value.
  +
  +In the job `spec` file, the `templates` block contains key/value pairs where:
  +
  +* Each key is template name
  +* Each value is the path to the corresponding file on a job VM
   
   The file paths that you provide for templates are relative to
  -the `/var/vcap/jobs` directory on the VM.
  -
  -When you write:
  -
  -~~~
  -bin/ctl
  -~~~
  -
  -That is transformed at compile time, into:
  -
  -~~~
  -/var/vcap/jobs/<job_name>/bin/ctl
  -~~~
  +the `/var/vcap/jobs/<job_name>` directory on the VM.
  +For example, `bin/ctl` becomes `/var/vcap/jobs/<job_name>/bin/ctl` on the job VM.
  +Using `bin` as the directory where theses files go is a convention.
   
   In our example, we edit the `spec` files for the both the `web_ui` and `bg_worker` jobs.
   The updated `spec` file for the `bg_worker` job looks like this:
  
positive.code: resulting binaries and scripts to the BOSH install target directory.
  BOSH creates the install target directory on a compilation VM, and then
  replicates it on a job VM.
  Then BOSH deletes the compilation VM.
  When you create the [deployment manifest](./create-manifest.html#compilation),
  you decide how many compilation VMs to create and how they should behave.
  
  
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>`
  
  