Merge pull request #5518 from EnterpriseDB/docs/edits_to_pgd_pr5477

Edits to PGD PR5477

product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx

@@ -36,7 +36,7 @@ Column-level conflict resolution requires the table to have `REPLICA IDENTITY FU
 ## Enabling and disabling column-level conflict resolution
 
 !!! Note Permissions required
-Column-level conflict detection uses the `column_timestamps` type. This requires the user to have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned to them.
+Column-level conflict detection uses the `column_timestamps` type. This type requires any user needing to detect column-level conflicts to have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned.
 !!!
 
 The [bdr.alter_table_conflict_detection()](conflicts#bdralter_table_conflict_detection) function manages column-level conflict resolution.

product_docs/docs/pgd/5/consistency/crdt.mdx

@@ -7,8 +7,8 @@ redirects:
 
 Conflict-free replicated data types (CRDT) support merging values from concurrently modified rows instead of discarding one of the rows as traditional resolution does.
 
-!!! Note Permissions Required
-PGD CRDT require usage access to CRDT types, therefore a user must have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned to them.
+!!! Note Permissions required
+PGD CRDT requires usage access to CRDT types. Therefore any user needing to access CRDT types must have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned to them.
 !!!
 
 Each CRDT type is implemented as a separate PostgreSQL data type with an extra callback added to the `bdr.crdt_handlers` catalog. The merge process happens inside the PGD writer on the apply side without any user

product_docs/docs/pgd/5/durability/camo.mdx

@@ -217,9 +217,9 @@ If status of the transaction wasn't success or connection was bad, we check if t
 
 ### Working with the CAMO partner
 
-!!! Note Permissions Required
-A number of the following CAMO functions require permission. Any user wishing to use CAMO, 
-the user must have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) 
+!!! Note Permissions required
+A number of the following CAMO functions require permission. Any user wanting to use CAMO 
+must have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) 
 role assigned to them.
 !!!
 

product_docs/docs/pgd/5/sequences.mdx

@@ -19,9 +19,9 @@ produce values that are unique only on the local node. This is important because
 unique ids generated by such sequences cause conflict and data loss by
 means of discarded `INSERT` actions in multi-master replication.
 
-!!! Note Permissions Required
-PGD global sequences are on by default. This means that for any user to use sequences, 
-the user must have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) 
+!!! Note Permissions required
+This means that any user who wants to use sequences
+must have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) 
 role assigned to them.
 !!!
 

product_docs/docs/pgd/5/striggers.mdx

@@ -13,9 +13,9 @@ data processing on the downstream/target node:
 
 Together, these types of triggers are known as *stream triggers*.
 
-!!! Note Permissions Required 
-Stream triggers are a PGD feature which requires
-permission. Any user wishing to create or drop triggers must have at least the
+!!! Note Permissions required 
+Stream triggers are a PGD feature that requires
+permission. Any user wanting to create or drop triggers must have at least the
 [bdr_application](security/pgd-predefined-roles/#bdr_application) role assigned
 to them. 
 !!!