anchor.diff:  
   Parts of any given BOSH manifest are IaaS-specific.
   Most manifest content, though, is independent of the cloud infrastructure where you want to deploy.
  -This allows you to re-use manifests, making minimal changes, even when moving a deployment from one IaaS to another.
  -
  -A BOSH deployment manifest begins with three dashes, and then identifies the deployment as follows:
  -
  -1. The **name** you give the deployment.
  -1. The `director_uuid` to ensure that you deploy with the correct BOSH.
  +This allows you to re-use manifests with minimal changes, even you re-deploy on a different IaaS.
  +
  +You begin the BOSH deployment manifest with three dashes, followed by the name you give the deployment,
  +then a `director_uuid` that ensures that you deploy with the correct BOSH.
   
   For example:
   
  
positive.code: 
  After that, the manifest has seven required _blocks_:
  
  1. releases
  1. compilation
  1. update
  1. resource_pools
  1. networks
  1. jobs
  1. properties
  
  The manifest is in YAML, so the YAML parser translates each block into a hash.
  For this reason, you can put the blocks in any order.
  
  <pre class="terminal">
  releases:
  
negative.code: 
  Features (templates) typically require configuration.
  You specify this information in the `properties` block.
  
  For example:
  
  <pre class="terminal">
  jobs:
  