anchor.diff:  job:
   
   * `with pidfile`: Name and path to the file containing the process ID (PID)
  -* `start program`: Command monit uses to start the process
  -* `stop program`: Command monit uses to stop the process
  +* `start program`: Command `monit` uses to start the process
  +* `stop program`: Command `monit` uses to stop the process
   
   See the [monit file example](#running-jobs).
  - 
  -**Note**: When developing or testing a release, you can use an empty `monit`
  -file.
  +
  +<p class="note"><strong>Note</strong>: When developing or testing a release, you can use an empty `monit` file.</p>
   
   #### <a id="errand-monitoring"></a>Errand Monitoring ####
   
  
positive.code: 1. Sends all output of the errand to the BOSH CLI for output
  1. Releases the deployment lock
  1. Releases the VM back into the resource pool
   
  Use `bosh run errand ERRAND-NAME` to run an errand. ERRAND-NAME must be the name of an errand provided in the deployment manifest.
  
  Example:
  
negative.code: 
  <pre class='terminal'>
  $ run errand SampleErrand --download-logs --logs-dir ~/workspace/SampleLogDirectory
  </pre>