anchor.diff:  ## <a id="blobs"></a> Add Blobs ##
   
   When creating a release, you likely use a source code repository.
  -
  -But releases often also use tar files or other binaries, also known as blobs.
  -For example, `ardo-release` uses libyaml.
  +But releases often use tar files or other binaries, also known as blobs.
   Checking blobs into a repository may be problematic if the repository you use
   is not well-suited to dealing with large binaries.
   (Git, for example, is not.)
  
positive.code: 
  * The `private.yml` file specifies the blobstore path, along with a secret.
  
  `private.yml` contains keys for accessing the blobstore.
  For that reason, `private.yml` is automatically gitignored (assuming you used the `--git`
  option when running `git init release` at the beginning of this tutorial).
  By not checking `private.yml` into Git, BOSH keeps the keys private.
  
  The `config` directory also contains two files whose content is automatically
  generated: the `blobs.yml` file and the `dev.yml` file.
  
negative.code: There is never `blobstore_secret` line for blobstores of types other than
  `local`.
  
  The `local` type blobstore is essentially a convenience for
  development.
  Final releases should use a non-local blobstore that is publicly accessible.
  
  ### <a id="inform"></a> Inform BOSH where blobs are ###
  
  In the package `spec` file, the `files` block lists any binaries you downloaded,
  along with the URLs from which you downloaded them.
  (This assumes that you followed the directions in the [Update package specs](#update-pkging-specs) section.)
  
  Those files are blobs, and now you need the paths to the downloaded blobs on
  