You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ta...@apache.org on 2015/06/11 20:11:46 UTC
qpid-jms git commit: QPIDJMS-72: fix a couple minor spelling errors.
Repository: qpid-jms
Updated Branches:
refs/heads/master 2e965a38c -> bd28bc7ed
QPIDJMS-72: fix a couple minor spelling errors.
Project: http://git-wip-us.apache.org/repos/asf/qpid-jms/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-jms/commit/bd28bc7e
Tree: http://git-wip-us.apache.org/repos/asf/qpid-jms/tree/bd28bc7e
Diff: http://git-wip-us.apache.org/repos/asf/qpid-jms/diff/bd28bc7e
Branch: refs/heads/master
Commit: bd28bc7ed2f34276a2cfac1de910c0af26ce6046
Parents: 2e965a3
Author: Timothy Bish <ta...@gmail.com>
Authored: Thu Jun 11 13:59:08 2015 -0400
Committer: Timothy Bish <ta...@gmail.com>
Committed: Thu Jun 11 14:03:43 2015 -0400
----------------------------------------------------------------------
qpid-jms-docs/Configuration.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/qpid-jms/blob/bd28bc7e/qpid-jms-docs/Configuration.md
----------------------------------------------------------------------
diff --git a/qpid-jms-docs/Configuration.md b/qpid-jms-docs/Configuration.md
index d35962e..d9e777e 100644
--- a/qpid-jms-docs/Configuration.md
+++ b/qpid-jms-docs/Configuration.md
@@ -29,7 +29,7 @@ Applications use a JNDI InitialContext, itself obtained from an InitialContextFa
a file, which is passed using the *java.naming.provider.url* system property. The syntax for these properties is detailed
below.
-3. Programatically using an environment Hashtable.
+3. Programmatically using an environment Hashtable.
The InitialContext may also be configured directly by passing an environment during creation:
@@ -205,7 +205,7 @@ The URI options for the multicast discovery agent are listed below:
The client makes use of the SLF4J API, allowing users to select a particular logging implementation based on their needs by supplying a SLF4J 'binding', such as *slf4j-log4j* in order to use Log4J. More details on SLF4J are available from http://www.slf4j.org/.
-The client uses Logger names residing within the *org.apache.qpid.jms* heirarchy, which you can use to configure a logging implementation based on your needs.
+The client uses Logger names residing within the *org.apache.qpid.jms* hierarchy, which you can use to configure a logging implementation based on your needs.
When debugging some issues, it may sometimes be useful to enable additional protocol trace logging from the Qpid Proton AMQP 1.0 library. There are two options to achieve this:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org