diff --git a/artemis-distribution/src/main/resources/README.html b/artemis-distribution/src/main/resources/README.html index b708568237..d9fb198265 100644 --- a/artemis-distribution/src/main/resources/README.html +++ b/artemis-distribution/src/main/resources/README.html @@ -97,7 +97,7 @@ e.g.

$ ./artemis run --config xml:/home/artemis/bootstrap.xml

-It is possible to configure run time paramters in the artemis.conf (artemis.conf.bat for windows) file under the "bin" directory of the broker directory. +It is possible to configure run time parameters in the artemis.conf (artemis.conf.bat for windows) file under the "bin" directory of the broker directory.

Stopping the Broker

diff --git a/examples/features/ha/application-layer-failover/readme.html b/examples/features/ha/application-layer-failover/readme.html index b60a66d5e8..c5248aade5 100644 --- a/examples/features/ha/application-layer-failover/readme.html +++ b/examples/features/ha/application-layer-failover/readme.html @@ -36,7 +36,7 @@ under the License. This listener will then be called by ActiveMQ Artemis in the event that connection failure is detected.

User code in the ExceptionListener can then recreate any JMS Connection, Session, etc on another node and the application can continue.

-

Application-Layer failover is an alternative approach to High Availabilty (HA).

+

Application-Layer failover is an alternative approach to High Availability (HA).

Application-Layer failover differs from automatic failover in that some client side coding is required in order to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted work in the old Session will be lost, and any unacknowledged messages might be redelivered.

diff --git a/examples/features/standard/jms-bridge/readme.html b/examples/features/standard/jms-bridge/readme.html index 1ee0ff6b00..182f7fa625 100644 --- a/examples/features/standard/jms-bridge/readme.html +++ b/examples/features/standard/jms-bridge/readme.html @@ -48,7 +48,7 @@ under the License.

JMS Bridge Configuration

The JMS Bridge is a POJO that we configure with both source and target - JNDI configurations. In the actual example we are programatically creating the Bridge, however the following section + JNDI configurations. In the actual example we are programmatically creating the Bridge, however the following section describes how you would do this if you wanted to deploy with an actual ActiveMQ Artemis server via the activemq-beans.xml.

Configuring the Bridge with the JBoss Microcontainer