diff --git a/product_docs/docs/pgd/5/consistency/crdt/02_state-op-crdts.mdx b/product_docs/docs/pgd/5/consistency/crdt/02_state-op-crdts.mdx
index 294450bdb65..4bda54c8064 100644
--- a/product_docs/docs/pgd/5/consistency/crdt/02_state-op-crdts.mdx
+++ b/product_docs/docs/pgd/5/consistency/crdt/02_state-op-crdts.mdx
@@ -20,7 +20,7 @@ The main disadvantage is that you can't reset this value reliably in an asynchro
 
 !!! Note
     Implementing more complicated operation-based types by creating custom data types is possible, storing the state and the last operation. (Every change is decoded and transferred, so multiple
-    operations aren't needed.) But at that point, the main benefits (simplicity, reuse of existing data types) are lost and no advantage gained compared to state-based types except for the space requirements. (A per-node state isn't needed.) For example, there's still no ability to reset. 
+    operations aren't needed.) But at that point, the main benefits (simplicity, reuse of existing data types) are lost and no advantage is gained compared to state-based types except for the space requirements. (A per-node state isn't needed.) For example, there's still no ability to reset. 
 
 ## State-based CRDT types (CvCRDT)
 
diff --git a/product_docs/docs/pgd/5/consistency/crdt/05_crdt-reset.mdx b/product_docs/docs/pgd/5/consistency/crdt/05_crdt-reset.mdx
index d928679621a..457ee01b5b7 100644
--- a/product_docs/docs/pgd/5/consistency/crdt/05_crdt-reset.mdx
+++ b/product_docs/docs/pgd/5/consistency/crdt/05_crdt-reset.mdx
@@ -7,7 +7,7 @@ Resetting CRDT values is possible but requires special handling. The asynchronou
 cluster means that different nodes might see the reset operation at different places in the change stream no matter how it's implemented. Different nodes might also initiate a reset concurrently, that is, before
 observing the reset from the other node.
 
-In other words, for the reset operation to behave correctly, it needs to be commutative with respect to the regular operations. Many naive ways to reset a value that might work well on a single-node fail
+In other words, for the reset operation to behave correctly, it needs to be commutative with respect to the regular operations. This is the reason why apparently straightforward ways of resetting a value that may work well on a single-node fail will not work correctly in other scenarios.
 for this reason.
 
 ## Challenges when resetting CRDT values