anchor.diff:  
   `bosh run errand <errand_name>`
   
  -where `<errand_name>` is a job name provided in deployment manifest. This will compile all the packages required by the errand job and execute the `run` script provided by the release for the errand.
  +In this command, `<errand_name>` is a job name provided in deployment manifest. This will compile all the packages required by the errand job and execute the `run` script provided by the release for the errand.
   
   The output of an errand will be printed on the screen once the errand is finished.
   
  
positive.code: 
  ### How to Deploy an Errand
  
  A BOSH errand has a similar structure as a regular BOSH job in a BOSH release. The Errand job in BOSH release should provide `run` script that will be executed as part of errand run.
  
  In the deployment manifest, a BOSH errand must have the `lifecycle` property set to `errand` in job description (see the example below). The resource pool must also provide enough capacity to accommodate an ephemeral VM for the errand.
  
  ### Example of an Errand Script
  
  
negative.code: 
  ### What is an Errand?
  
  A BOSH Errand is a short lived BOSH job that operator can run multiple times after a deploy has finished. Common use cases include:
  
  * Smoke tests
  * Cloud Foundry Service Broker binding and unbinding
  