Doc 4309

modules/eventing/pages/eventing-Terminologies.adoc

@@ -119,3 +119,4 @@ Newly created handlers start in an undeployed state.
 
 When a Function gets deleted, the source code implementing the Function, all processing checkpoints, and other artifacts in the metadata provider are purged.
 Before deleting, make sure you have undeployed the Function.
+

modules/eventing/pages/eventing-debugging-and-diagnosability.adoc

@@ -116,17 +116,19 @@ Couchbase Server creates different application log files depending on the level
 NOTE: The *cbcollect_info* tool does not collect the Application log files.
 
 .Application Logs Path in Platform
+[cols="20%,80%"]
 |===
 | Platform | Location
 
 | Linux
 | /opt/couchbase/var/lib/couchbase/data/@eventing
 
 | Windows
-| C:\Program Files\Couchbase\Server\var\lib\couchbase\data\@eventing (Assumes default installation location)
+| C:\Program Files\Couchbase\Server\var\lib\couchbase\data\@eventing +
+(Assumes default installation location)
 
 | Mac OS X
-| /Users/<user>/Library/Application Support/Couchbase/var/lib/couchbase/data/@eventing
+| /Users/<user>/Library/Application Support/Couchbase/var/lib/ couchbase/data/@eventing
 |===
 
 To configure an Application log, use the REST endpoint settings option.
@@ -165,11 +167,15 @@ You can use logs for multiple purposes ranging from security, monitoring, and di
 Suppression of sensitive data such as personally identifiable information (PII), hostnames, internal asset information, credit card details, during the logging operation is termed as log redaction.
 Organizations implement log redaction as part of their legal compliance and security risk mitigations.
 
+
 Couchbase Server provides a capability to redact sensitive user data from getting captured in the logs.
 All sensitive data are scrubbed and gets removed from the log files.
 Post redaction, log files can be shared for troubleshooting without disregarding any regulatory compliance.
 
+NOTE: Log redaction is applicable only for System logs and not for Application logs.
+
 For details, see xref:clustersetup:logging.adoc#understanding_redaction[Understanding Redaction].
+
 // <ol>
 // <li>From the Couchbase Web Console Logs tab, select <uicontrol>Collect
 // Information</uicontrol>.</li>

modules/eventing/pages/eventing-faq.adoc

@@ -146,6 +146,7 @@ These are the meta fields associated with the document. For more information, re
 
 * What is the metadata bucket? Do I need to create a separate bucket?
 +
+
 To provide better restartability semantics when an Eventing node is offline, some metadata needs to be stored: a Couchbase bucket solves this problem.
 Setting up the metadata bucket is a one-time activity that is done cluster-wide.
 It is recommended that the metadata bucket not be used for any other data-storage (which is to say, it should not be accessed by any other application).

modules/eventing/pages/eventing-language-constructs.adoc

@@ -156,7 +156,6 @@ SELECT * FROM `beer-sample` WHERE type...
 ----
 SELECT * FROM beersample WHERE type ...
 ----
-
 [#handler-signatures]
 == Handler Signatures