From 39b5bc8a8456235540730c88922f60855a16e46b Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Sun, 12 Oct 2014 15:48:18 +0000 Subject: QPID-6108: [Java Broker Documentation] Rewrite HA documentation to reflect the new model and the include multi-node support. * Correct many spelling errors * Improve web-console documentation around add/edit/delete entities, and the setting of context variables * Extract new top level section for backup/recovery git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1631195 13f79535-47bb-0310-9956-ffa450edef68 --- .../java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'qpid/doc/book/src/java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml') diff --git a/qpid/doc/book/src/java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml b/qpid/doc/book/src/java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml index 7b7928fda0..7d3d62b075 100644 --- a/qpid/doc/book/src/java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml +++ b/qpid/doc/book/src/java-broker/Java-Broker-Appendix-Operational-Logging-Messages.xml @@ -28,7 +28,7 @@ Operational Logging The Broker will, by default, produce structured log messages in response to key events in - the lives of objects within the Broker. These consise messages are designed to allow the user to + the lives of objects within the Broker. These concise messages are designed to allow the user to understand the actions of the Broker in retrospect. This is valuable for problem diagnosis and provides a useful audit trail. Each log message includes details of the entity causing the action (e.g. a management user @@ -1196,7 +1196,7 @@ - The node is no longer reachanble. This may be as a result of the node being + The node is no longer reachable. This may be as a result of the node being stopped or a network partition may be preventing it from being connected. The node is still a member of the group. -- cgit v1.2.1