anchor.diff:  
   `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
  +The `bosh add blob` command adds a local blob to the collection 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
  +* For the second argument, you provide a destination within 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
  +which BOSH makes in a hidden directory
   
   Using the package name as the second argument of the `bosh add blobs` command
   is recommended because it produces a cleanly-organized blobs directory.
  
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: For example, a start command can take a property as an argument,
  using a variable of the form:
  
  	<%%= properties.<job_name>.<property_name> %>
  
  1. Specify the property in the [deployment manifest](./create-manifest.html#properties).
  
  Adapt the example below to create any properties your release needs now.
  
  In our example, we want the port that the web UI listens on to be a
  configurable property.
  