From ee2a08cfdd326d4eea867484680eb4ca594d3c22 Mon Sep 17 00:00:00 2001
From: ibsoln <52778946+ibsoln@users.noreply.github.com>
Date: Thu, 6 May 2021 09:42:25 +0100
Subject: [PATCH] QF210506-3 -- line 40 change
 https://issues.couchbase.com/browse/DOC-8390

---
 modules/ROOT/pages/server-compatibility-eventing.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/ROOT/pages/server-compatibility-eventing.adoc b/modules/ROOT/pages/server-compatibility-eventing.adoc
index bb8306ec7..945a05a05 100644
--- a/modules/ROOT/pages/server-compatibility-eventing.adoc
+++ b/modules/ROOT/pages/server-compatibility-eventing.adoc
@@ -45,9 +45,9 @@ This is necessary because:
 But when an update originates outside of Couchbase mobile then multiple mutations are generated.
 That is because Sync Gateway must update both the document's body and its _sync metadata (XATTRs).
 
-* _Eventing_ detects these mutations and invokes its `OnUpdate` *for each*; whether it is for the modified body of the document, XATTRs, or both.
+* _Eventing_ detects these mutations and invokes its `OnUpdate` *for each*; whether it is for the modified body of the document, Sync Gateway metadata, or both.
 It is here that you need to code the function to apply the same update once only.
-One way to do this is to use the crc64 function call -- see: {server-eventing-constructs-crc64--xref} for more on how to do this.
+One way to do this is to use the crc64 function call to identify when an update is to the Sync Gateway metadata only -- see: {server-eventing-constructs-crc64--xref} for more on how to do this.
 
 _Eventing_ prevents inadvertent use of its functions on _Sync Gateway_ read-write buckets.
 You will see the following  warning if you try to do this: +