anchor.diff:  
   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.
  +* 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.
  +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
  
positive.code: 
  <pre class='terminal'>
  $ run errand SampleErrand --download-logs --logs-dir ~/workspace/SampleLogDirectory
  </pre>
  
  
negative.code: 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`.
  
  <p class="note"><strong>Note</strong>: Since BOSH releases the VM back into the resource pool when an  errand completes, you cannot access any log files or screen output after this process finishes.</p>
  
  By default, BOSH streams errand output smaller than 1MB, stdout, and stderr to
  the screen.
  You must redirect errand output greater than 1MB to a file.
  
  To save output from a BOSH errand VM:
  
  1. In the BOSH errand script, redirect the output 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.
  