diff --git a/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/07_auto_conflict_resolution_eg.mdx b/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/07_auto_conflict_resolution_eg.mdx
index ec5f1bac61a..64a1b60ea60 100644
--- a/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/07_auto_conflict_resolution_eg.mdx
+++ b/product_docs/docs/eprs/7/06_mmr_operation/06_conflict_resolution/07_auto_conflict_resolution_eg.mdx
@@ -86,6 +86,6 @@ __OUTPUT__
 
 ## Update/update conflict on primary key columns
 
-An update/update conflict on the primary key column might not resolve consistently resolved according to the selected resolution option. That is, the column values might differ for the same row across multiple primary nodes after the synchronization replication.
+An update/update conflict on the primary key column might not resolve consistently according to the selected resolution option. That is, the column values might differ for the same row across multiple primary nodes after the synchronization replication.
 
 In addition, this conflict might not appear under the **Conflict History** tab in the Replication Server console. Even if a conflict resolution entry does appear under the **Conflict History** tab, the actual primary key values might not be consistent across the nodes as implied by the conflict resolution.