There are some minor bugs in Configuring Messaging [1] docs:

(1) 2.5. About JMS Destinations
Applications may have use many different JMS destinations which are configured on the server side and usually accessed via JNDI.
==>
Applications may use

(2) 3.2.3. JNDI Entries and Clients
A Queue or Topic must be bound to the java:jboss/exported namespace for a remote client to be able look it up.
==> to be able to look it up

(3) 3.2.3. JNDI Entries and Clients
You can use the find more information about the jms-queue and jms-topic commands by using the --help --commands flags
==>
You can find more information

(4) 4.7.5.2. Configure a Generic JMS Resource Adapter for Use with a Third-party JMS Provider
There are some JMS provider (such as Tibco EMS) that do not support the JNDI lookup(Name) method.
==> There are some JMS providers

[1] https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/configuring-messaging/