diff --git a/modules/eventing/pages/eventing-Terminologies.adoc b/modules/eventing/pages/eventing-Terminologies.adoc
index a6288c892d..71af085860 100644
--- a/modules/eventing/pages/eventing-Terminologies.adoc
+++ b/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.
+
diff --git a/modules/eventing/pages/eventing-debugging-and-diagnosability.adoc b/modules/eventing/pages/eventing-debugging-and-diagnosability.adoc
index 1fe56a640a..45bc9c0ac8 100644
--- a/modules/eventing/pages/eventing-debugging-and-diagnosability.adoc
+++ b/modules/eventing/pages/eventing-debugging-and-diagnosability.adoc
@@ -129,6 +129,9 @@ NOTE: The *cbcollect_info* tool does not collect the Application log files.
 | /Users/<user>/Library/Application Support/Couchbase/var/lib/couchbase/data/@eventing
 |===
 
+
+NOTE: During Cluster setup, if you have chosen a custom path, then the path for Application logs is same as that of the selected Indexes Path. The @eventing folder in the selected Indexes Path stores the Application logs.
+
 To configure an Application log, use the REST endpoint settings option.
 
 *Sample URL*: `192.168.1.5:8091/_p/event/api/v1/functions/<Function_name>/settings`
diff --git a/modules/eventing/pages/eventing-faq.adoc b/modules/eventing/pages/eventing-faq.adoc
index 515ec3771c..72f871e301 100644
--- a/modules/eventing/pages/eventing-faq.adoc
+++ b/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).
@@ -178,3 +179,4 @@ When the Eventing node experiences a failover condition, few mutations may be pr
 * Does a rebalance have any effect on the firing of events?
 +
 No. Functions do not lose any mutations during a rebalance operation.
+
diff --git a/modules/eventing/pages/troubleshooting-best-practices.adoc b/modules/eventing/pages/troubleshooting-best-practices.adoc
index ef6f49df96..ae9766bf9a 100644
--- a/modules/eventing/pages/troubleshooting-best-practices.adoc
+++ b/modules/eventing/pages/troubleshooting-best-practices.adoc
@@ -76,3 +76,4 @@ Ensure that you configure the script timeout value after carefully evaluating th
 
 As a best practice use a combination of try-catch block and the application log options.
 This way you can monitor, debug and troubleshoot errors during the Function execution.
+