anchor.diff:  For example, a start command can take a property as an argument,
   using a variable of the form:
   
  -1. Specify the property in the deployment manifest.
  +	<%%= 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.
  
positive.code: 
  ### <a id="upload-blobs"></a> Upload blobs ###
  
  You are ready to do a final release except for one thing:
  your latest dev release depends on locally-stored blobs.
  
  Before you go further, run `bosh blobs`.
  Proofread the list of blobs to make sure
  it includes nothing but the blobs you need for the final release.
  
  If some file that you need to keep private is mistakenly
  uploaded to a blobstore, there is no satisfactory way to
  undo the error.
  
  Now you can upload your blobs to a blobstore:
  
    `bosh upload blobs`
  
  ### <a id="final-commit"></a> Commit ###
  
  You have run the `bosh upload blobs` command so the `blobs` file now contains names and keys.
  
  This is a good time to commit.
  
  ### <a id="final-release-release"></a> Release ###
  
  
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  ##
  
  