anchor.diff:  
   In the manifest you specify orchestration along with everything else about your deployment,
   including the stemcell, release, and network configuration to use.
  +
  +**Note**: This topic does not treat using multiple releases or stemcells for simplicity's sake, but BOSH supports both.
   
   ## <a id="release"></a> Translating from Release to Manifest ##
   
  
positive.code: 1. jobs
  1. properties
  
  Manifests are written in YAML, which means that each block is translated into a hash.
  You can put the blocks in any order.
  
  ### <a id='compilation'></a> The compilation block ###
  
  BOSH compiles all the software packages within the release at deploy time.
  The `compilation` block specifies which VMs should perform the compilation.
  
  ### <a id='update'></a> The update block ###
  
  The `update` block:
  
negative.code: * A BOSH release uses the term "job" to describe a _feature_.
  * Meanwhile, a BOSH manifest uses the term "job" to describe a _VM type_,
  and the term "template" to describe a feature.
  
  When you allocate a feature to a VM type, the feature described as a "job" in the release becomes a "template" in the `jobs` block in the manifest.
  You name your VM types as "jobs" and specify a number of instances for each.
  
  In the illustration below, five features found in a release are allocated to VM types in a manifest.
  