anchor.diff:  
   This block is IaaS-dependent, because subnets, network names, and other keys may differ from IaaS to IaaS.
   
  -### <a id='jobs'></a> The jobs block ###
  +### <a id='resources'></a> The resources block ###
   
  -The `jobs` block is where you name VM types and specify:
  -
  -* The product features each type supports, in the form of templates.
  -* Some configuration information that applies to the VM type as opposed to the feature.
  -
  -Features (templates) typically require configuration.
  -You specify this information in the `properties` block.
  -
  -For example:
  +The resources block lists
   
   <pre class="terminal">
  -jobs:
  -- name: dummy
  -  templates:
  -  - name: dummy
  -    release: dummy_a
  -  instances: 1
  -  resource_pool: default
  -  persistent_disk: 10240
  -  networks:
  -  - name: default
  +resources:
  +
   </pre>
   
  -This block is IaaS-agnostic.
  +### <a id='cloud'></a> The cloud block ###
   
  -### <a id='properties'></a> The properties block ###
  +
  +### <a id='apply'></a> The apply_spec 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.
  
positive.code: 
  </pre>
  
  This block is IaaS-dependent.
  
  ## <a id="example"></a> Example Manifests ##
  
  BOSH provides a [variety](https://github.com/cloudfoundry/bosh/tree/master/release/examples) of example manifests.
  
  ## <a id="creating"></a> How to Create a Manifest ##
  
  You can modify example manifests to suit your purposes. Another approach is to use a tool like [spiff](https://github.com/cloudfoundry-incubator/spiff) to create a manifest.
  
  
negative.code: title: Creating a MicroBOSH Deployment Manifest
  ---
  
  The deployment manifest for MicroBOSH is similar the deployment manifest for multi-VM BOSH,
  but much smaller.
  
  Parts of the manifest are IaaS-specific.
  