anchor.diff:  
   After that, the manifest has seven required _blocks_:
   
  -1. releases
  -1. compilation
  -1. update
  -1. resource_pools
  -1. networks
  -1. jobs
  -1. properties
  +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.
  +
  +### <a id='releases'></a> The releases block ###
  +
  +The release block lists the name and version of each release you use in your deployment:
  +
  +For example:
   
   <pre class="terminal">
   releases:
  
positive.code:     availability_zone: us-east-1c
  </pre>
  
  ### <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.
  
  <pre class="terminal">
  networks:
  
negative.code:   version: 0.1-dev
  </pre>
  
  This block is IaaS-agnostic.
  
  ### <a id='compilation'></a> The compilation block ###
  
  At deploy time, BOSH compiles all the software packages within the release.
  The `compilation` block specifies which VMs should perform the compilation.
  
  For example:
  
  <pre class="terminal">
  compilation:
  