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: 
  ### <a id="no-upload"></a> Do not upload blobs for a dev release ###
  
  The nature of blobstores (other than local ones) is that once you have uploaded blobs,
  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`.
  That command is discussed below, in connection with final releases.
  
  ## <a id="create-props"></a> Create Job Properties  ##
  
  
negative.code: 
  BOSH prompts you for a release name, and assigns a whole-number version to the release.
  
  This is a good time to push your code to a shared repository to give others access to
  your final release.
  
  ### <a id="final-release-commit"></a> Commit ###
  
  