Merge pull request #3165 from EnterpriseDB/docs/pgd/removing-group-co…

…mmit-note

PGD: soften language against using legacy options

product_docs/docs/pgd/4/bdr/durability.mdx

@@ -45,9 +45,7 @@ Postgres provides [Physical Streaming Replication](https://www.postgresql.org/do
 For backward compatibility, BDR still supports configuring synchronous
 replication with `synchronous_commit` and `synchronous_standby_names`. See
 [Legacy synchronous replication](durability#legacy-synchronous-replication-using-bdr),
-but the use of [Group Commit](group-commit) is recommended instead
-in all cases.
-
+but consider using [Group Commit](group-commit) instead.
 ## Terms and definitions
 
 BDR nodes can take different
@@ -108,7 +106,7 @@ Postgres crashes.*
 `synchronous_replication_availability` to `async'`, otherwise the
 values for the asynchronous BDR default apply.*
 
-*(3) Not recommended. Consider using Group Commit instead.*
+*(3) Consider using Group Commit instead.*
 
 Reception ensures the peer operating normally can
 eventually apply the transaction without requiring any further
@@ -208,8 +206,7 @@ required synchronization level and prevents loss of data.
 ## Legacy synchronous replication using BDR
 
 !!! Note
-    We don't recommend this approach.  Consider using
-    [Group Commit](group-commit) instead.
+    Consider using [Group Commit](group-commit) instead.
 
 ### Usage