anchor.diff:  ## monit                                     #
   ## --8<--
   ##
  -## You can override the alert message format or its parts such as subject
  +## You can override this message format or parts of it, such as subject
   ## or sender using the MAIL-FORMAT statement. Macros such as $DATE, etc.
  -## are expanded on runtime. For example to override the sender:
  +## are expanded at runtime. For example, to override the sender:
   #
   # set mail-format { from: monit@foo.bar }
  -set mail-format {from:info@engineyard.com}
  -
  -#
  -#
  -## You can set the alert recipients here, which will receive the alert for
  -## each service. The event alerts may be restricted using the list.
  +#
  +#
  +## You can set alert recipients here whom will receive alerts if/when a 
  +## service defined in this file has errors. Alerts may be restricted on 
  +## events by using a filter as in the second example below. 
   #
   # set alert sysadm@foo.bar                       # receive all alerts
   # set alert manager@foo.bar only on { timeout }  # receive just service-
   #                                                # timeout alert
  -
  -set alert eymonit@gmail.com only on { timeout, nonexist }
  -
  -#
  -#
  -## Monit has an embedded webserver, which can be used to view the 
  -## configuration, actual services parameters or manage the services using the 
  -## web interface.
  +#
  +#
  +## Monit has an embedded web server which can be used to view status of 
  +## services monitored, the current configuration, actual services parameters
  +## and manage services from a web interface.
   #
   # set httpd port 2812 and
   #     use address localhost  # only accept connection from localhost
   #     allow localhost        # allow localhost to connect to the server and
   #     allow admin:monit      # require user 'admin' with password 'monit'
   #
  -
  -set httpd port 9111
  -    allow localhost
  -
   #
   ###############################################################################
   ## Services
   ###############################################################################
   ##
  -## Check the general system resources such as load average, cpu and memory
  -## usage. Each rule specifies the tested resource, the limit and the action
  -## which will be performed in the case that the test failed.
  +## Check general system resources such as load average, cpu and memory
  +## usage. Each test specifies a resource, conditions and the action to be
  +## performed should a test fail.
   #
   #  check system myhost.mydomain.tld
   #    if loadavg (1min) > 4 then alert
  
positive.code: #
  #    
  ## Check a file for existence, checksum, permissions, uid and gid. In addition
  ## to the recipients in the global section, customized alert will be send to 
  ## the additional recipient. The service may be grouped using the GROUP option.
  #    
  #  check file apache_bin with path /usr/local/apache/bin/httpd
  #    if failed checksum and 
  
negative.code: #    group server
  #    
  #    
  ## Check device permissions, uid, gid, space and inode usage. Other services,
  ## such as databases, may depend on this resource and an automatically graceful
  ## stop may be cascaded to them before the filesystem will become full and data
  ## lost.
  #
  #  check device datafs with path /dev/sdb1
  #    start program  = "/bin/mount /data"
  