anchor.diff:  
   #### <a id="canceling-jobs"></a>Canceling Errands ####
   
  -Use `bosh cancel errand ERRAND_NAME` to cancel a running errand.
  -
  -Example:
  +Use `bosh cancel task <task_id>` to cancel a running errand.
   
   <pre class="terminal">
  -$ bosh cancel errand my-smoke-test
  +$ bosh cancel task 123
   </pre>
   
   The `bosh cancel errand` command terminates the errand process, releases the
   deployment lock, and returns the errand VM to the resource pool.
   
   #### <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.
  
positive.code: ## <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 during the duration of the errand.
  * Currently, BOSH limits errand output to 1MB. BOSH discards errand output greater than 1MB.
negative.code: 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:
  
  