anchor.diff:  If this property is not set, BOSH uses the default value `service` and
   configures instances of the job to run as long as the deployment runs.
   
  -
  -**Notes**: 
  -
  -* Since BOSH requests and provisions a new VM for each errand, the
  +<p class="note"><strong>Notes</strong>:
  +  <ul>
  +    <li>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.
  - 
  +per errand. If you receive an error message about insufficient VM capacity, you must adjust the <a href="./deployment-manifest.html#jobs">Jobs Block</a> of your deployment manifest.</li>
  +	<li>Errands do not have a notion of persistence. Persistent disk migration for errands is not supported.</li>
  +  </ul>
  +</p>
   
   ## <a id="job-parts"></a>Parts of a BOSH Job or BOSH Errand ##
   
  
positive.code: 
  A job specification, or **spec**, is a YAML document that lists:
  
  * 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, a package 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 ###
  
  Templates contain information shared across jobs or errands, such as account 
  names and passwords. Templates consist of plain text and Ruby code for variable 
  substitution and flow control. BOSH evaluates these templates as Ruby ERB 
  template files when creating an instance of a job.
  
  At compile time, BOSH uses job templates to create the control scripts and
  configuration files that the BOSH [agent](./terminology.html#agent) needs to run
  
negative.code: 
  ## <a id="running"></a>Running Jobs and Errands ##
  
  BOSH ensures an instance of a job or errand always runs in a predictable,
  deterministic environment by creating a new VM specifically for the instance.
  
  ### <a id="running-jobs"></a>Running Jobs ###
  
  BOSH creates instances of the job on VMs as part of the deployment process.
  BOSH monitors the instances it deploys and restarts any that fail, keeping them
  running for as long as the deployment runs.
  
  BOSH runs jobs using the commands provided in the `monit` file.
  