Hi Jared,

I've found some inconsistencies in HornetQ User Guide for EAP 5.1.2:

1. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch02s08.html
should be completed completed with
-->
should be completed with

2. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch03s02.html
Once it is done that, it acknowledges the messages
-->
Once it is done, it acknowledges the message

3. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch03s08.html
Degrees of support for clusters varies
-->
Degree of support for clusters varies

4. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/persistence.html
Any resources configures with configuration files are not.
-->
Any resources configured with configuration files are not.

5. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch19s02.html
Once the messages have be unsuccessfully delivered
-->
Once the messages have been unsuccessfully delivered

6. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/message-expiry.configuring.html
Expiry address are defined
-->
Expiry addresses are defined

7. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/queue-attributes.html
This is very similar to the JMS configuration, but with three real differences which are listed here:
-->
This is very similar to the JMS configuration, but with four real differences which are listed here:

8. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch26s03.html
Any messages sent will be not be delivered
-->
Any sent messages will not be delivered

These means that grouping can still occur on fail-over.
-->
This means that grouping can still occur on fail-over.

9. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch28s03.html
send a management reply to the management message's reply-to addresses
-->
sends a management reply to the management message's reply-to address

10. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/management.jms.html
All the other steps are the same than for the Core API but they use JMS API instead:
-->
All the other steps are the same as for the Core API but they use JMS API instead:

11. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/management.message-counters.html
because there are as many messages sent to the queue than messages consumed from it
-->
because there are as many messages sent to the queue as messages consumed from it

Message counters keeps a history of the queue metrics (10 days by default) and samples all the queues at regular interval
-->
Message counters keep a history of the queue metrics (10 days by default) and sample all the queues at regular interval

12. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch30s02.html
Heres an example
-->
Here is an example

13. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch31s04s04.html
JBoss uses Sun's RMI and the properties can be found here.
document http://java.sun.com/j2se/1.5.0/docs/guide/rmi/sunrmiproperties.html does not exist

14. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/clusters.html
Also discussed is client side load balancing, where client connections can be balanced across the nodes of the cluster.
-->
There is also discussed client side load balancing, where client connections can be balanced across the nodes of the cluster.

15. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/clusters.server-discovery.html
The connector to be broadcasted is specified by the connector-name attribute, and the backup connector to be broadcasted is specified by the backup-connector attribute.
-->
The connector to be broadcast is specified by the connector-name attribute, and the backup connector to be broadcast is specified by the backup-connector attribute.

16. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/clusters.discovery-groups.html
connector information is broadcasted
-->
connector information is broadcast

By messaging clients so they can discovery what servers in the cluster they can connect to.
-->
By messaging clients so they can discover what servers in the cluster they can connect to.

17. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/clusters.server-discovery.html
name attribute
-->
name

OR

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch36s02s03.html
name
-->
name attribute

18. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/clusters-discovery.groups.clientside.html
http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch36s02s04s02.html
it may not have had enough time to received broadcasts
-->
it may not have had enough time to receive broadcasts

19. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch36s03.html
If no cluster connection was defined on node A, as order messages arrive on node A they will all end up in the OrderQueue on node A, so will only get consumed by the order processor client attached to node A, Pa.
-->
If no cluster connection was defined on node A, as order messages arrive on node A they will all end up in the OrderQueue on node A, so they will only get consumed by the order processor client attached to node A, Pa.

20. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/High_Availability_and_Fail_Over.html
After a live server has failed and a backup taken has taken over its duties,
-->
After a live server has failed and a backup server has taken over its duties,

21. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/failover.html
Alternatively, the clients can explicitly specifies pairs of live-backup server
-->
Alternatively, the clients can explicitly specify pairs of live-backup server

any subsequent attempt to commit it will throw
-->
any subsequent attempt to commit will throw

22. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/EAP_HornetQ_Clusters.html
http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/ch38s02.html
Specifies the multiplier <retry-interval> uses for each subsequent reconnection pauses.
-->
Specifies the multiplier <retry-interval> used for each subsequent reconnection pauses.

Ensure the file is well-formed from an XML validation perspective by ensure the XML Namespace is present and correct in the file as specified.
-->
Ensure the file is well-formed from an XML validation perspective by ensuring the XML Namespace is present and correct in the file as specified.

23. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/Intercepting_Operations.html
A interceptor
-->
An interceptor

25. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/HornetQ_User_Guide/interoperability.html
Stomp clients are available for several languages and platforms making it a good choice for interoperability.
page http://stomp.github.com//Clients does not exist

StompConnect is a server that can act as a Stomp broker
page http://stomp.github.com//StompConnect does not exist

Could you please look at it?

Thank you,

Nikoleta