From c0ec7e2ff8621f76551cb9fe5e49a92c1919652d Mon Sep 17 00:00:00 2001 From: Pat Fox Date: Mon, 23 May 2016 17:40:42 +0200 Subject: [PATCH] a few tiny doc typos --- docs/user-manual/en/jms-bridge.md | 2 +- docs/user-manual/en/paging.md | 2 +- docs/user-manual/en/send-guarantees.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user-manual/en/jms-bridge.md b/docs/user-manual/en/jms-bridge.md index daa7017f34..fc8c9c187e 100644 --- a/docs/user-manual/en/jms-bridge.md +++ b/docs/user-manual/en/jms-bridge.md @@ -26,7 +26,7 @@ JMS servers, as long as they are JMS 1.1 compliant. > > Do not confuse a JMS bridge with a core bridge. A JMS bridge can be > used to bridge any two JMS 1.1 compliant JMS providers and uses the -> JMS API. A core bridge (described in [Core Bidges](core-bridges.md)) is used to bridge any two +> JMS API. A core bridge (described in [Core Bridges](core-bridges.md)) is used to bridge any two > Apache ActiveMQ Artemis instances and uses the core API. Always use a core bridge if > you can in preference to a JMS bridge. The core bridge will typically > provide better performance than a JMS bridge. Also the core bridge can diff --git a/docs/user-manual/en/paging.md b/docs/user-manual/en/paging.md index a7252e221d..6b5ddb5efc 100644 --- a/docs/user-manual/en/paging.md +++ b/docs/user-manual/en/paging.md @@ -115,7 +115,7 @@ This is the list of available parameters on the address settings. `page-max-cache-size` - The system will keep up to \<`page-max-cache-size` page files in memory to optimize IO during paging navigation. + The system will keep up to `page-max-cache-size` page files in memory to optimize IO during paging navigation. 5 diff --git a/docs/user-manual/en/send-guarantees.md b/docs/user-manual/en/send-guarantees.md index d4add028d2..95a355c5cf 100644 --- a/docs/user-manual/en/send-guarantees.md +++ b/docs/user-manual/en/send-guarantees.md @@ -101,7 +101,7 @@ server and the client of 0.25 ms. With a RTT of 0.25 ms, the client can send *at most* 1000/ 0.25 = 4000 messages per second if it blocks on each message send. -If each message is \< 1500 bytes and a standard 1500 bytes MTU size is +If each message is < 1500 bytes and a standard 1500 bytes MTU (Maximum Transmission Unit) size is used on the network, then a 1GiB network has a *theoretical* upper limit of (1024 \* 1024 \* 1024 / 8) / 1500 = 89478 messages per second if messages are sent without blocking! These figures aren't an exact