Gardening

Mostly tech-debt errors carried over from earlier versions of this doc.

Author: RichardSmedley

modules/howtos/pages/collecting-information-and-logging.adoc

@@ -11,7 +11,7 @@ The Couchbase Java SDK logs events and also provides an event bus that transmits
 
 == Logging
 
-The Couchbase Java SDK uses https://www.slf4j.org[SLF4J], a logging facade that lets you use any logging framework that has an SLF4J binding.
+The Couchbase Java SDK uses https://www.slf4j.org[SLF4J], a logging façade that lets you use any logging framework that has an SLF4J binding.
 This includes popular Java logging frameworks like Log4j, Logback, and `java.util.logging` (JUL).
 
 To see log messages from the Couchbase SDK, add an SLF4J binding as a dependency of your project.
@@ -195,7 +195,8 @@ Dedicated logging frameworks like Log4j 2 and Logback are more configurable, and
 [NOTE]
 .Event Bus Stability
 ====
-While the event bus functionality itself is considered stable, the events itself may not be. Please only consume the events you are interested in, and add error handling code in case of unexpected behaviour.
+While the event bus functionality itself is considered stable, the events themselves may not be. 
+Please only consume the events you are interested in, and add error handling code in case of unexpected behavior.
 ====
 
 Log files are neither fun to wade through, nor do they have any kind of real-time aspect.
@@ -204,7 +205,8 @@ Since most setups interleave all different kinds of log messages, it makes it ve
 
 To make the situation better and ultimately improve supportability, the Java SDK provides you with the ability to tap into all events before they get logged and consume them in "real-time".
 
-You can subscribe to the event bus, and receive and react to events as they are happening; not when someone parses the logs, sends them into another system where an alarm is triggered, and eventually a sysadmin checks what iss going on.
+You can subscribe to the event bus, and receive and react to events as they are happening; 
+not when someone parses the logs, sends them into another system where an alarm is triggered, and eventually a sysadmin checks what is going on.
 The time delta between an event happening and reacting to it can thus be substantially decreased.
 
 The following code subscribes to the event bus and prints out all events that are published on it with INFO or WARN level:
@@ -224,12 +226,14 @@ NodeConnectedEvent{severity=INFO, category=com.couchbase.node, duration=PT0S, cr
 BucketOpenedEvent{severity=INFO, category=com.couchbase.core, duration=PT0.281625729S, createdAt=43701036027888, description=Opened bucket "travel-sample", context=CoreContext{coreId=1}, cause=null}
 ----
 
-We recommend filtering on the specific events you are interested in, since most of the time only a subset of the published ones will be of use to you. Also, there are new events added between releases so make sure these new events do not break your functionality.
+We recommend filtering on the specific events you are interested in, since most of the time only a subset of the published ones will be of use to you. 
+Also, there are new events added between releases so make sure these new events do not break your functionality.
 
 [WARNING]
 .Blocking Warning
 ====
-If you consume the `EventBus` you MUST NOT block inside the consumer callback. It will stall all other consumers. If you must write into a blocking sink like a blocking HTTP API you MUST write it onto a different thread with a non-blocking queue first.
+If you consume the `EventBus` you MUST NOT block inside the consumer callback. It will stall all other consumers. 
+If you must write into a blocking sink like a blocking HTTP API you MUST write it onto a different thread with a non-blocking queue first.
 ====
 
 
@@ -246,6 +250,6 @@ include::example$CollectingInformationAndLogging.java[tag=collecting_information
 Different redaction levels are supported -- please see the `RedactionLevel` enum description for more information.
 
 Note that you need to run this command before any of the SDK code is initialized so all of the logs are captured properly. 
-Once the SDK writes the logs with the tags to a file, you can then use the xref:7.1@server:cli:cbcli/cblogredaction.adoc[`cblogredaction` tool] to obfuscate the log.
+Once the SDK writes the logs with the tags to a file, you can then use the xref:7.2@server:cli:cbcli/cblogredaction.adoc[`cblogredaction` tool] to obfuscate the log.
 
-* You may wish to read more on Log Redaction xref:7.1@server:manage:manage-logging/manage-logging.adoc#understanding_redaction[in the Server docs].
+* You may wish to read more on Log Redaction xref:7.2@server:manage:manage-logging/manage-logging.adoc#understanding_redaction[in the Server docs].