diff --git a/product_docs/docs/pgd/5.8/conflict-management/conflicts/03_conflict_detection.mdx b/product_docs/docs/pgd/5.8/conflict-management/conflicts/03_conflict_detection.mdx
index fda6f616dfe..f1c9fbd42e8 100644
--- a/product_docs/docs/pgd/5.8/conflict-management/conflicts/03_conflict_detection.mdx
+++ b/product_docs/docs/pgd/5.8/conflict-management/conflicts/03_conflict_detection.mdx
@@ -61,7 +61,7 @@ PGD provides the option to use row versioning and make conflict detection indepe
 
 Row version conflict detection requires that you enable three things. If any of these steps aren't performed correctly then [origin conflict detection](#origin-conflict-detection) is used.
 
--  Enable `check_full_tuple` or the PGD node group.
+-  Enable `check_full_tuple` on the PGD node group.
 
 -  Enable `REPLICA IDENTITY FULL` on all tables that use row version conflict detection.
 
@@ -77,4 +77,4 @@ This approach resembles Lamport timestamps and fully prevents the ABA problem fo
 
 To determine the current conflict detection strategy used for a specific table, refer to the column `conflict_detection` of the view `bdr.tables`.
 
-To change the current conflict detection strategy, use [bdr.alter_table_conflict_detection](../../reference/conflict_functions/#bdralter_table_conflict_detection).
\ No newline at end of file
+To change the current conflict detection strategy, use [bdr.alter_table_conflict_detection](../../reference/conflict_functions/#bdralter_table_conflict_detection).