anchor.diff:  configures instances of the job to run as long as the deployment runs.
   
   Common BOSH errands include any task meant to be run once or only on demand.
  -Examples include:
  -
  -* Smoke tests
  -* Binding or unbinding a Cloud Foundry service broker
  +Examples include smoke tests and Cloud Foundry service broker binding.
  +
  +**Notes**:
  +
  +* Since BOSH requests and provisions a new VM for each errand, the
  +resource pool for a BOSH deployment with errands must include one additional VM
  +per errand. If you receive an error message about insufficient VM capacity, you
  +must adjust the [Job Block](./deployment-manifest.html#jobs) of your deployment
  +manifest.
  +* Errands do not have a notion of persistence. Persistent disk migration for errands is not supported.
  +
   
   ## <a id="job-parts"></a>Parts of a BOSH Job or BOSH Errand ##
   
  
positive.code: 
  * Required [packages](./reference/packages.html): A package contains source code and a script. The script describes how to compile the source code and install the resultant binary. Optionally, packages can contain the names of other packages this package depends on.
  * Job templates: The names and file paths to [job templates](#templates) that the job uses.
  * Job properties: BOSH uses job properties when creating an instance of a job. Typical job properties include account names, passwords, shared secrets, hostnames, IP addresses, port numbers, and descriptions.
  
  ### <a id="templates"></a>Templates ###
  
  
negative.code: 
  ## <a id="jobs-vs-errands"></a>Errands ##
  
  An **errand** is a type of BOSH job that runs once or only on demand.
  
  To distinguish an errand from a job, set the `lifecycle` property for
  the errand in the [Jobs Block](./deployment-manifest.html#jobs) of the
  