activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] activemq-artemis git commit: fixed minor formatting typos
Date Mon, 20 Jun 2016 10:45:58 GMT
Repository: activemq-artemis
Updated Branches:
  refs/heads/master a39f43dfe -> efdafb092

fixed minor formatting typos


Branch: refs/heads/master
Commit: 0ce077eea1917415de846d70cb08419e612e0925
Parents: a39f43d
Author: Lionel Cons <>
Authored: Mon Jun 20 09:37:11 2016 +0200
Committer: Lionel Cons <>
Committed: Mon Jun 20 09:37:11 2016 +0200

 docs/user-manual/en/ | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/docs/user-manual/en/ b/docs/user-manual/en/
index 1e18b4d..872fe2f 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -256,10 +256,9 @@ Netty for simple TCP:
     small number of consumers, but at the cost of overall throughput and
     scalability - especially on multi-core machines. If you want the
     lowest latency and a possible reduction in throughput then you can
-    use the default value for `directDeliver` (i.e. true). If you are
+    use the default value for `directDeliver` (i.e. `true`). If you are
     willing to take some small extra hit on latency but want the highest
-    throughput set `directDeliver` to `false
-                            `.
+    throughput set `directDeliver` to `false`.
 -   `nioRemotingThreads`. When configured to use NIO, Apache ActiveMQ Artemis will,
     by default, use a number of threads equal to three times the number
@@ -422,6 +421,6 @@ additional properties:
 -   `httpServerScanPeriod`. How often, in milliseconds, to scan for
     clients needing responses
--   `httpRequiresSessionId`. If true the client will wait after the
+-   `httpRequiresSessionId`. If `true` the client will wait after the
     first call to receive a session id. Used the http connector is
     connecting to servlet acceptor (not recommended)

View raw message