anchor.diff:       default: 80
   ~~~
   
  -Adapt the example to create any properties your release needs now.
  -
   ## <a id="dev-release"></a> Do a Dev Release  ##
   
   All the elements needed to create a dev release should now be in place.
   
   ### <a id="dev-release-release"></a> Release  ###
   
  -For a dev release, BOSH needs to use the local copies of our blobs.
  -Use the `--force` option with the `bosh create release` command,
  -because otherwise BOSH expects the blobs to have been uploaded first,
  -and we do not want to upload blobs until we a final release.
  -
  -Using the `--force` option is permissible when creating and testing dev
  -releases but not final releases.
  +For the dev release, use the `--force` option with the `bosh create release`
  +command.
  +This forces BOSH to use the local copies of our blobs.
  +
  +Without the `--force` option, BOSH requires blobs to be uploaded before you
  +run `bosh create release`.
  +For a final release, we upload blobs, but not for a dev release.
   
   Create the dev release:
   
  
positive.code: 
  `bosh add blob <path_to_blob_on_local_system> <package_name>`
  
  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.
  
negative.code: 
  ### <a id="no-upload"></a> Do not upload blobs for a dev release ###
  
  Once you have uploaded blobs to a non-local blobstore, those blobs may become
  essential to some other developer.
  For this reason, uploading a blob and then removing it is considered poor practice.
  
  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> Create Job Properties  ##
  
  