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: Example:
  
  <pre class="terminal">
  $ bosh run errand my-smoke-test-errand
  </pre>
  
  The `bosh run errand` command compiles all packages the errand job requires and executes the `run` script that the BOSH release provides for the errand.
  
  **Example Executable Script**
  
  This is an example `run` script for a BOSH errand that de-registers a service
  broker.
  
  <pre class='terminal'>
  
negative.code: 
  An operator runs a BOSH errand using the `bosh run errand` command.
  To facilitate this, an errand defined in a BOSH release should provide an
  executable /bin/run script.
  
  Whenever an errand runs, BOSH:
  
  