[2/2] activemq-artemis git commit: NO-JIRA fix JMS destination cache doc

[jb...@apache.org]

NO-JIRA fix JMS destination cache doc


Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/ed095a05
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/ed095a05
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/ed095a05

Branch: refs/heads/master
Commit: ed095a0523f58b305e90952ab2782fcf87a1602a
Parents: 83d363d
Author: Justin Bertram <jb...@apache.org>
Authored: Tue Jun 12 10:34:31 2018 -0500
Committer: Justin Bertram <jb...@apache.org>
Committed: Wed Jun 13 21:57:15 2018 -0500

----------------------------------------------------------------------
 docs/user-manual/en/perf-tuning.md | 2 +-
 docs/user-manual/en/using-jms.md   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/ed095a05/docs/user-manual/en/perf-tuning.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/perf-tuning.md b/docs/user-manual/en/perf-tuning.md
index 3b2d37a..19c2595 100644
--- a/docs/user-manual/en/perf-tuning.md
+++ b/docs/user-manual/en/perf-tuning.md
@@ -139,7 +139,7 @@ some tuning:
   then you can avoid some unnecessary copying.
   
 - If using frameworks like Spring, configure destinations permanently broker
-  side and enable `destinationCache` on the client side.  See the [Setting The
+  side and enable `cacheDestinations` on the client side.  See the [Setting The
   Destination Cache](using-jms.md) for more information on this.
 
 ## Tuning Transport Settings

http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/ed095a05/docs/user-manual/en/using-jms.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/using-jms.md b/docs/user-manual/en/using-jms.md
index bc9f3f2..2634266 100644
--- a/docs/user-manual/en/using-jms.md
+++ b/docs/user-manual/en/using-jms.md
@@ -393,7 +393,7 @@ valuable bandwidth. This can be configured on the connection factory via the
 Many frameworks such as Spring resolve the destination by name on every
 operation, this can cause a performance issue and extra calls to the broker, in
 a scenario where destinations (addresses) are permanent broker side, such as
-they are managed by a platform or operations team.  using `destinationCache`
+they are managed by a platform or operations team.  using `cacheDestinations`
 element, you can toggle on the destination cache to improve the performance and
 reduce the calls to the broker.  This should not be used if destinations
 (addresses) are not permanent broker side, as in dynamic creation/deletion.