anchor.diff:  * Find the official site for the binary in question.
   For example, Ruby might be at `http://cache.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p484.tar.gz`.
   
  -* Download the binary from the official location and make sure the md5 hashes match.
  +* Download the binary from the official location and make sure the file hash matches.
   
   * Record the binary name including version number, with a slash and the binary filename concatenated to it.
  -In the same line, cite the official URL in a comment.
  -
  -BOSH interprets the locations you record in the `files` section as being in the `blobs` directory.
  -In the next few steps, you will add the actual blobs to a local blobstore, which will populate the
  -`blobs` directory with the correct information.
  +It's a good idea to cite the official URL in a comment, in the same line.
  +
  +BOSH interprets the locations you record in the `files` section as being either in the `src` directory or
  +in the `blobs` directory. (BOSH looks in `src` first).
  +When you add the actual blobs to a local blobstore (see the next section), BOSH populates the `blobs` directory with the
  +correct information.
   
   Observe how these conventions are followed in the examples.
   
  
positive.code: * Up to now all we have is a mention of the package in the job spec.
  * Now we create the job package itself:
  
    `bosh generate package ardo-web`
  
  * The package contains a `spec` and a `packaging` script, both empty when
  the package is newly created.
  * Next, put useful information into `spec` and `packaging`.
  
  ### <a id="..."></a> Update the job package spec with dependency information ###
  
negative.code: packaging script.
  
  For a start on writing packaging scripts, study the examples.
  Begin packaging scripts with a `set -e -x` line to aid debugging at compile time.
  
  _explicitly say to write all packaging scripts now?_
  _include packaging scripts inline?_
  
  ### <a id="..."></a> Create packaging specs ###
  
  Within each package directory is a `spec` file which states:
  
  * The package name.
  * The package's dependencies.
  * The location where BOSH can find the binaries and other files that the package needs.
  
  Use your dependency graph to determine which dependencies belong in each spec.
  
  