anchor.diff:  
   == AutoResolve triggers
   
  -A trigger definition has one or multiple conditions that are set to detect a problem. When incoming data matches the
  -condition expresions an alert is triggered to inform about this new issue. In this context, if the engine is still
  +A trigger has one or multiple conditions that are set to detect a problem. When incoming data matches the
  +condition expresions an alert is fired to inform about this new issue. In this context, if the engine is still
   receiving data, new alerts will be generated even if it refers to the *same* problem.
   
   The detection of multiple alerts belonging to the *same* problem can be controlled with fine granularity.
  
positive.code: 
  == Alert Lifecycle
  
  Alert definitions (triggers) are used to detect problems. When a problem happens a new alert is generated by the engine
  with the information about the data that matched the defined conditions. Also an Alert provides a simple lifecycle to
  indicate the status of the problem.
  
  
negative.code: 
  <1> *autoResolve* flag set to *true* indicates that the trigger will activate *FIRING* and *AUTORESOLVE* modes. Flag set
  to *false* will run the trigger only in *FIRING* mode.
  <2> *autoResolveAlerts* flag set to *true* will automatically mark all unresolved alerts (for the trigger) as *resolved*
  when *AUTORESOLVE* trigger detect problem is gone. Flag set to *false* will not modify the alert lifecycle.
  
  And the next fragment will show how to declare *FIRING* and *AUTORESOLVE* conditions linked with the trigger:
  
  