Description of problem:

March 09 2010 Test Day - Alerts - Documentation review

??? is there anyway to turn on line numbers for the rhq wiki ??? 
??? is it still appropriate to link to JOPR doc ???

 * Alert creation documentation already exists here(which is ok if you intended to rewrite it.):
   * https://www.redhat.com/docs/en-US/JBoss_ON/2.3/html/Feature_Guide/chap-Feature_Guide-Alerts.html (includes conditions, dampening, etc)  (
   * Your documentation seems to be more complete then the documentation listed in these links, however there is duplication.
   * https://www.redhat.com/docs/en-US/JBoss_ON/2.3/html/Feature_Guide/sect-Feature_Guide-Events-Defining_Alerts_on_Events.html
   * https://www.redhat.com/docs/en-US/JBoss_ON/2.3/html/Feature_Guide/sect-Feature_Guide-Monitoring_Defaults-Alert_Templates.html
 * Sections 1.3.2 and 1.3.3  - should be reversed; knowing how to create alerts themselves should preface creating alert templates.  Especially evident given "Brief Introduction to Alerts and Notifications" subsection in 1.3.3.  
 * Include additional alert sender methods:  && update Default Alert Senders two
   * RHQ has several different methods of sending a notification:
     * Email
     * IRC (chat)
     * Microblogging (such as Twitter and Laconica)
     * Mobicents (voice mail)
     * SNMP traps
     * Operations
     * Roles
     * ScriptLang
 * Section 1.3.4 - enumerated list should be expanded onto multiple lines
 * Section 1.3.7 - "Wild cards (*) and other expressions are allowed." seems awkward/incomplete. (found in "Viewing Alert Definitions" and "Viewing Alerts" subsections)
 * Section 1.3.9 - fix  "&VER;" references
 * Section 1.3.9 - "Migrating alerts from older versions of Jopr is not (officially) supported"  -- strike "(officially)" or find a better way to phrase this.
 * Section 1.3.9 (and presumably elsewhere) - is there some convention for writing out filenames, i.e., dumpAlertDefinitions.js, alertDefinitions.csv?
 * Notifications section - It is also possible to write custom alert methods, which are implemented as server-side plug-ins. For more information on writing plug-ins, see XREF - fix XREF
 * Somehow rephrase  Automatic Responses (Operations)  
   * maybe.... Automatic Response - using operations to perform actions in response to alerts... 
 * Strike "In RHQ, alert notifications allow that kind of clustering." in tooltip
 * Change "It is also possible to acknowledge a single alert through the alert detail's page." to "It is also possible to acknowledge a single alert through the alert details page."
 * Section 1.3.6.2: "Four results elements are important for organizing the definitions:"...  I think that 'attributes' might be a better descriptor for 'results elements'...  also, why are these important and how do they organize definitions?
 * Comma splices:
   * "When an alert is acknowledged, the name of the user who acknowledged the alert is recorded, so the action can be audited later if necessary." - between recorded and so
   * "Select the Resources menu in the top navigation bar, and select the Servers menu item." - bet
 * 
 * "Despite the name, the operations performed in response to an alert are not the same as the operations which can be scheduled to run on a resource." - we don't know what this means.  as far as we know, they ARE the same.
 * 
 * 
 * Change "To create a template alert definition:" to "Creating an Alert Definition Template" in bold to match its counterpart heading "Creating an Alert Sender Template"
 * 
 * You listed a question..  Alert Notification templates  can be found http://server:7080/rhq/resource/alert/notif/notificationTemplates.xhtml

 * 
 * 
 *  change XREF in  Click the Edit Alert Templates button to create a global alert definition. Set up the alert exactly the same way as setting an alert for a single resource (as in XREF).
 * Please change 
   * Brief Introduction to Alerts and Notifications
   * An alert is a configuration that lets an administrator know that something is happened ===> to something has happened
 * SSHD => sshd, there is no need to put in caps


----
Server Side Plugins:
 * "GUI plug-ins for customizing workflows within the server interface or for getting additional functionality in the GUI" - I'm not sure this is still true, are these plugins still going to be part of RHQ?