anchor.diff:      availability_zone: us-east-1c
   </pre>
   
  +This block contains an IaaS-dependent `cloud_properties` sub-block.
  +
   ### <a id='networks'></a> The networks block ###
   
  -IaaS-dependent -- some have subnet, some have network names, some keys differ
  -
   The `networks` block is where you specify network configuration information for the deployment.
  -Networks are named, enabling you to specify multiple networks.
  +You can specify multiple networks.
  +
  +For example:
   
   <pre class="terminal">
   networks:
  
positive.code: 
  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.
  
  For example:
  
  
negative.code:     default: [dns, gateway]
  </pre>
  
  This block is IaaS-agnostic.
  
  ### <a id='properties'></a> The properties block ###
  
  The `properties` block consists of headings followed by one or more lines of configuration information.
  Most headings are names of features (templates) from the `jobs` block.
  
  This block can be quite long, so the example below shows only a few interesting excerpts.
  
  <pre class="terminal">
  properties:
  