small change.

EnterpriseDB · Sep 5, 2024 · c25af0d · c25af0d
1 parent fa9fec0
commit c25af0d
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx b/product_docs/docs/pgd/5.6/reference/commit-scopes.mdx
@@ -49,7 +49,9 @@ Where `node_group` is the name of a PGD data node group.
 
 ## Commit scope targets
 
-Instead of targeting a specific PGD data node group, you can target `ORIGIN_GROUP` to create a rule that applies to the node group of *any* transaction-originating data node in the cluster, simplifying the rule definition by covering multiple groups simultaneously. For example, supposing you have two groups `right_dc` and `left_dc`, instead of having one rule `MAJORITY (left_dc)` and another rule `MAJORITY (right_dc)`, you can just use the one rule `MAJORITY ORIGIN_GROUP` that will apply to both groups.
+Instead of targeting a specific PGD data node group, you can target `ORIGIN_GROUP` to create a rule that applies to the node group of *any* transaction-originating data node in the cluster, simplifying the rule definition by covering multiple groups simultaneously. 
+
+For example, supposing you have two groups `right_dc` and `left_dc`, instead of having one rule `MAJORITY (left_dc)` and another rule `MAJORITY (right_dc)`, you can just use the one rule `MAJORITY ORIGIN_GROUP` that will apply to both groups.
 
 ## Commit scope groups