anchor.diff:  
   `bosh add blob <path_to_blob_on_local_system> <package_name>`
   
  -BOSH adds each blob to the `blobs` directory, in a subdirectory whose name is the
  -second argument to the `bosh add blob` command.
  -The package name is a good choice for that argument because it produces a
  -cleanly-organized `blobs` directory.
  +The `bosh add blob` command adds a local blob file to the collection of files your release
  +recognizes as BOSH blobs.
  +
  +The usage shown above is a blend of requirement and convention.
  +It works like this:
  +
  +* For the first argument, you provide the path to the blob on your local system
  +* For the second argument, you provide the destination in the `blobs` directory in
  +your release
  +* BOSH goes into the `blobs` directory and creates a subdirectory with
  +the name of the package that the local blob represents
  +* In the new subdirectory, BOSH creates a symbolic link to a copy of the blob
  +which BOSH makes within a hidden directory in the release
  +
  +Using the package name as the second argument of the `bosh add blobs` command
  +is recommended because it produces a cleanly-organized blobs directory.
  +
  +Later, when you upload blobs for a final release, BOSH uses the hidden directory
  +as a staging area.
   
   ### <a id="no-upload"></a> Do not upload blobs for a dev release ###
   
  
positive.code: ## <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.
  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.)
  
negative.code: BOSH lets you avoid checking blobs into a repository by doing the following:
  
  * For dev releases, use local copies of blobs.
  
  * For a final release, upload blobs to a blobstore, and direct BOSH to obtain the blobs from there.
  
  ### <a id="config-blobstore"></a> Configure a blobstore  ###
  