Changed sentence in reference describing ultiple_unique_constraints.

product_docs/docs/pgd/5.6/conflict-management/conflicts/02_types_of_conflict.mdx

@@ -326,9 +326,12 @@ You can take one of the following actions:
 
 ## Exclusion constraint conflicts
 
-With the addition of `EXCLUDE` constraint support in PGD 5.6, there's an increased risk of replication issues due to  multi-row conflicts. If a replicated row violates an `EXCLUDE` constraint by conflicting with multiple existing rows on the target node, replication can halt until the conflict is resolved. 
+With the addition of `EXCLUDE` constraint support in PGD 5.6, there's an increased risk of replication issues due to  multi-row conflicts.
+If a replicated row violates an `EXCLUDE` constraint by conflicting with an existing row on the target node, replication can halt until the conflict is resolved.
 
-In case of such a conflict, whether from and `INSERT` or `UPDATE`, you must remove some rows for replication to continue. Depending on the resolver setting for `multiple_unique_conflicts`, the apply process either exits with error, skips the incoming row, or deletes some of the rows. The deletion tries to preserve the row with the correct `PRIMARY KEY` and delete the others.
+In case of such a conflict, whether from and `INSERT` or `UPDATE`, you must remove some rows for replication to continue.
+Depending on the resolver setting for `multiple_unique_conflicts`, the apply process either exits with error, skips the incoming row, or deletes some of the rows.
+The deletion tries to preserve the row with the correct `PRIMARY KEY` and delete the others.
 
 ## Data conflicts for roles and tablespace differences
 

product_docs/docs/pgd/5.6/reference/conflicts.mdx

@@ -18,7 +18,7 @@ PGD recognizes the following conflict types, which can be used as the `conflict_
 | `update_missing`          | An incoming update is trying to modify a row that doesn't exist.                              |
 | `update_recently_deleted` | An incoming update is trying to modify a row that was recently deleted.                       |
 | `update_pkey_exists`      | An incoming update has modified the `PRIMARY KEY` to a value that already exists on the node that's applying the change. |
-| `multiple_unique_conflicts` | The incoming row conflicts with multiple UNIQUE constraints/indexes in the target table and/or with multiple rows per an `EXCLUDE` index. |
+| `multiple_unique_conflicts` | The incoming row conflicts with either multiple `UNIQUE` constraints/indexes, a single `UNIQUE` constraint and a single `EXCLUDE` constraint, or with multiple rows per an `EXCLUDE` index in the target table. |
 | `delete_recently_updated` | An incoming delete with an older commit timestamp than the most recent update of the row on the current node or when using [row version conflict detection](../conflict-management/conflicts/03_conflict_detection/#row-version-conflict-detection). |
 | `delete_missing`          | An incoming delete is trying to remove a row that doesn't exist.                              |
 | `target_column_missing`   | The target table is missing one or more columns present in the incoming row.                  |