anchor.diff:  
   BOSH jobs consist of three parts: specifications, templates, and monitoring.
   
  -BOSH errands consist of two parts, specifications and templates.
  +BOSH errands consist of two parts: specifications and templates.
   BOSH does not monitor the health of any processes in instances of an errand.
   
   ### <a id="specification"></a>Specifications ###
   
   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, packages can contain the names of other packages this package depends on.
  +* 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.
  +* 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 ###
   
  
positive.code: 
  #### <a id="errand-logging"></a>Errand Logging ####
  
  BOSH names logs using the errand name and type of log, and writes the logs to
  the `/var/vcap/sys/log/<errand-name>` directory.
  
  For example, BOSH writes the stdout log for an errand named "smoke-test" to `/var/vcap/sys/log/smoke-test/smoke-test.stdout.log`.
  
  BOSH only logs errand output if the output is greater than 1MB in size.
  By default, BOSH streams smaller errand output, stdout, and stderr to the screen.
  
  When BOSH [runs an errand](#errand-running), BOSH provisions and configures a VM for the errand.
  When the errand completes, BOSH releases the VM back into the resource pool.
  Once the VM has been released back into the resource pool, you cannot access any log files or screen output on the VM.
  
  To save log files and screen output from a BOSH errand VM:
  
  1. In the BOSH errand script, redirect stdout and stderr to a log file.
  1. Using the BOSH CLI, run `bosh errand` with the `--download-logs` option to download the log files.
  
      By default, BOSH downloads the logs to your present working directory.
      Use the `--logs-dir destination_directory` option to change this
      directory.
  
      <pre class='terminal'>
      $ run errand SampleErrand --download-logs --logs-dir ~/workspace/SampleLogDirectory
      </pre>
  
  ## <a id="errand-running"></a>Warnings and Additional Information ##
  
  * Errands do not have a notion of persistence. Persistent disk migration for errands is not supported.
  * Whenever an errand runs, BOSH initiates a deployment lock. This lock prevent all other deploys. Additionally, the BOSH CLI `cloudcheck` command is unavailable, and the health monitor does not scan and fix current deployments while the errand runs.
  * Currently, BOSH limits errand output to 1MB by discarding any errand output greater than 1MB.
negative.code: 
  #### <a id="job-monitoring"></a>Job Monitoring ####
  
  BOSH uses [monit](http://mmonit.com/monit/) to manage and monitor the health of 
  processes in an instance of a job.
  Using monit, BOSH can start, stop, and restart instances of a job when
  necessary.
  
  