Merge pull request #5129 from EnterpriseDB/BDR-3696-Using-bdr.raft_gr…

…oup_max_connections-in-BDR-3.7

BDR 3.7 Documentation fixes

product_docs/docs/pgd/3.7/bdr/configuration.mdx

@@ -429,10 +429,14 @@ Unless noted otherwise, values may be set by any user at any time.
      Measure round trip time of a bdr consensus request and log an
      `INFO` message if the time exceeds this parameter. Default value
      of this parameter is 5000 ms.
--   `bdr.raft_group_max_connections` - The maximum number of connections
+-   `bdr.group_max_connections` - The maximum number of connections
      across all BDR groups for a Postgres server. These connections carry
      bdr consensus requests between the groups' nodes. Default value of this
      parameter is 100 connections. May only be set at Postgres server start.
+     BDR 3.7.13 and later will emit a warning when setting this variable
+     that it is deprecated and bdr.raft_group_max_connections should be used.
+     Ignore this warning and continue to use bdr.group_max_connections (until
+     you upgrade to BDR 4 and later).
 -   `bdr.backwards_compatibility` - Specifies the version to be
     backwards-compatible to, in the same numerical format as used by
     `bdr.bdr_version_num`, e.g. `30618`.  Enables exact behavior of a