Repository: activemq-artemis
Updated Branches:
  refs/heads/master a5beec7e2 -> 487cc4542

NO-JIRA fix typos in documentation


Branch: refs/heads/master
Commit: 060781d430b3d4aa8966e18c835081758386bff0
Parents: a5beec7
Author: Bennet Schulz <>
Authored: Fri Jun 16 10:58:23 2017 +0200
Committer: Bennet Schulz <>
Committed: Fri Jun 16 10:58:23 2017 +0200

 docs/user-manual/en/ | 2 +-
 docs/user-manual/en/        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/user-manual/en/ 
index 010c19f..6177384 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -6,7 +6,7 @@ performance.
 ## Tuning persistence
 -   To get the best performance from Apache ActiveMQ Artemis whilst
-    using perisistent messages it is recommended that the file store
+    using persistent messages it is recommended that the file store
     is used.  Apache ActiveMQ Artemis also supports JDBC persistence,
     but there is a performance cost when persisting to a database vs 
     local disk.
diff --git a/docs/user-manual/en/ b/docs/user-manual/en/
index 9034c39..e1766cd 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -5,7 +5,7 @@ scalability features of Apache ActiveMQ Artemis over a simple 
REST/HTTP interfac
 The REST Interface implementation sits on top of an Apache ActiveMQ Artemis 
 as such exposes JMS like concepts via REST.
-Using the REST internface Messages can produced and consumed by sending 
+Using the REST interface Messages can be produced and consumed by sending 
 and receiving simple HTTP messages that contain the content you want to push 
around. For instance,
 here's a simple example of posting an order to an order processing queue
 express as an HTTP message:

Reply via email to