more Acrolinx

Author: American-Dipper

articles/postgresql/flexible-server/concepts-pgbouncer.md

@@ -24,7 +24,7 @@ When enabled, PgBouncer runs on port 6432 on your database server. You can chang
 
 ## Enabling and configuring PgBouncer
 
-In order to enable PgBouncer, you can navigate to the “Server Parameters” blade in the Azure portal, and search for “PgBouncer” and change the pgbouncer.enabled setting to “true” for PgBouncer to be enabled. There is no need to restart the server. However, to set other PgBouncer parameters, see the limitations section.
+In order to enable PgBouncer, you can navigate to the “Server Parameters” blade in the Azure portal, and search for “PgBouncer” and change the pgbouncer.enabled setting to “true” for PgBouncer to be enabled. There's no need to restart the server. However, to set other PgBouncer parameters, see the limitations section.
 
 You can configure PgBouncer, settings with these parameters:
 
@@ -34,26 +34,26 @@ You can configure PgBouncer, settings with these parameters:
 | pgBouncer.max_client_conn | Set this parameter value to the highest number of client connections to PgBouncer that you want to support.     | 5000     | 
 | pgBouncer.pool_mode | Set this parameter value to TRANSACTION for transaction pooling (which is the recommended setting for most workloads).      | TRANSACTION     |
 | pgBouncer.min_pool_size | Add more server connections to pool if below this number.    |   0 (Disabled)   |
-| pgbouncer.ignore_startup_parameters | Comma-separated list of parameters that PgBouncer can ignore. For example, you can let PgBouncer ignore `extra_float_digits` parameter. Some parameters are allowed, all others raise error. This is needed to tolerate overenthusiastic JDBC wanting to unconditionally set 'extra_float_digits=2' in startup packet. Use this if the library you use report errors such as `pq: unsupported startup parameter: extra_float_digits`. |   |
-| pgbouncer.query_wait_timeout | Maximum time (in seconds) queries are allowed to spend waiting for execution. If the query is not assigned to a server during that time, the client is disconnected. | 120s |
+| pgbouncer.ignore_startup_parameters | Comma-separated list of parameters that PgBouncer can ignore. For example, you can let PgBouncer ignore `extra_float_digits` parameter. Some parameters are allowed, all others raise error. This ability is needed to tolerate overenthusiastic JDBC wanting to unconditionally set 'extra_float_digits=2' in startup packet. Use this option if the library you use report errors such as `pq: unsupported startup parameter: extra_float_digits`. |   |
+| pgbouncer.query_wait_timeout | Maximum time (in seconds) queries are allowed to spend waiting for execution. If the query isn't assigned to a server during that time, the client is disconnected. | 120s |
 | pgBouncer.stats_users | Optional. Set this parameter value to the name of an existing user, to be able to log in to the special PgBouncer statistics database (named “PgBouncer”).    |      |
 
-For more details on the PgBouncer configurations, see [pgbouncer.ini](https://www.pgbouncer.org/config.html).
+For more information about PgBouncer configurations, see [pgbouncer.ini](https://www.pgbouncer.org/config.html).
 
 > [!IMPORTANT]
 > Upgrading of PgBouncer is managed by Azure.
 
 ## Benefits and Limitations of built-in PGBouncer feature
 
-By leveraging the benefits of built-in PgBouncer with Flexible Server, users can enjoy the convenience of simplified configuration, the reliability of a managed service, support for various connection types, and seamless high availability during failover scenarios. Using built-in PGBouncer feature provides for following benefits:
- * As it's seamlessly integrated with Azure Database for PostgreSQL - Flexible Server service, there is no need for a separate installation or complex setup. It can be easily configured directly from the server parameters, ensuring a hassle-free experience. 
+By using the benefits of built-in PgBouncer with Flexible Server, users can enjoy the convenience of simplified configuration, the reliability of a managed service, support for various connection types, and seamless high availability during failover scenarios. Using built-in PGBouncer feature provides for following benefits:
+ * As it's seamlessly integrated with Azure Database for PostgreSQL - Flexible Server service, there's no need for a separate installation or complex setup. It can be easily configured directly from the server parameters, ensuring a hassle-free experience. 
  * As a managed service, users can enjoy the advantages of other Azure managed services. This includes automatic updates, eliminating the need for manual maintenance and ensuring that PgBouncer stays up-to-date with the latest features and security patches. 
- * The built-in PgBouncer in Flexible Server provides support for both public and private connections. This allows users to establish secure connections over private networks or connect externally, depending on their specific requirements. 
- * In the event of a failover, where a standby server is promoted to the primary role, PgBouncer seamlessly restarts on the newly promoted standby without any changes required to the application connection string. This ensures continuous availability and minimizes disruption to the application's connection pool. 
+ * The built-in PgBouncer in Flexible Server provides support for both public and private connections. This functionality allows users to establish secure connections over private networks or connect externally, depending on their specific requirements. 
+ * In the event of a failover, where a standby server is promoted to the primary role, PgBouncer seamlessly restarts on the newly promoted standby without any changes required to the application connection string. This ability ensures continuous availability and minimizes disruption to the application's connection pool. 
 
  There are following limitations with using this feature today:
  * PgBouncer is currently not supported with Burstable server compute tier. 
- * Transaction and statement connection pooling modes cannot be used along with prepared statements.
+ * Transaction and statement connection pooling modes can't be used along with prepared statements.
  * Only a subset of configuration parameters is available with built-in PGBouncer vs. standalone product. 
  * Whenever the server is restarted, the PgBouncer is also restarted along with the server. Hence, existing connections must be re-established. 
 
@@ -66,14 +66,14 @@ Azure Database for PostgreSQL - Flexible Server now provides six new metrics for
 
 |Display Name                            |Metrics ID                |Unit |Description                                                                          |Dimension   |Default enabled|
 |----------------------------------------|--------------------------|-----|-------------------------------------------------------------------------------------|------------|---------------|
-|**Active client connections** (Preview) |client_connections_active |Count|Connections from clients which are associated with a PostgreSQL connection           |DatabaseName|No             |
+|**Active client connections** (Preview) |client_connections_active |Count|Connections from clients that are associated with a PostgreSQL connection           |DatabaseName|No             |
 |**Waiting client connections** (Preview)|client_connections_waiting|Count|Connections from clients that are waiting for a PostgreSQL connection to service them|DatabaseName|No             |
 |**Active server connections** (Preview) |server_connections_active |Count|Connections to PostgreSQL that are in use by a client connection                     |DatabaseName|No             |
 |**Idle server connections** (Preview)   |server_connections_idle   |Count|Connections to PostgreSQL that are idle, ready to service a new client connection    |DatabaseName|No             |
 |**Total pooled connections** (Preview)  |total_pooled_connections  |Count|Current number of pooled connections                                                 |DatabaseName|No             |
 |**Number of connection pools** (Preview)|num_pools                 |Count|Total number of connection pools                                                     |DatabaseName|No             |
 
-To learn more, please refer [pgbouncer metrics](./concepts-monitoring.md#pgbouncer-metrics)
+To learn more, see [pgbouncer metrics](./concepts-monitoring.md#pgbouncer-metrics)
 
 ### Admin Console
 
@@ -98,7 +98,7 @@ For more details on the PgBouncer show command, please refer [Admin console](htt
 ## Switching your application to use PgBouncer
 
 In order to start using PgBouncer, follow these steps:
-1. Connect to your database server, but use port **6432** instead of the regular port 5432 -- verify that this connection works
+1. Connect to your database server, but use port **6432** instead of the regular port 5432--verify that this connection works
 ```azurecli-interactive
 psql "host=myPgServer.postgres.database.azure.com port=6432 dbname=postgres user=myUser password=myPassword sslmode=require"
 ```
@@ -121,10 +121,10 @@ Utilizing an application side pool together with PgBouncer on the database serve
 ## Limitations
 
 * PgBouncer is currently not supported with Burstable server compute tier. 
-* If you change the compute tier from General Purpose or Memory Optimized to Burstable tier, you will lose the PgBouncer capability.
+* If you change the compute tier from General Purpose or Memory Optimized to Burstable tier, you lose the PgBouncer capability.
 * Whenever the server is restarted during scale operations, HA failover, or a restart, the PgBouncer is also restarted along with the server virtual machine. Hence the existing connections have to be re-established.
-* Due to a known issue, the portal does not show all PgBouncer parameters. Once you enable PgBouncer and save the parameter, you have to exit Parameter screen (for example, click Overview) and then get back to Parameters page. 
-* Transaction and statement pool modes cannot be used along with prepared statements. Refer to the [PgBouncer documentation](https://www.pgbouncer.org/features.html) to check other limitations of chosen pool mode.
+* Due to a known issue, the portal doesn't show all PgBouncer parameters. Once you enable PgBouncer and save the parameter, you have to exit Parameter screen (for example, click Overview) and then get back to Parameters page. 
+* Transaction and statement pool modes can't be used along with prepared statements. Refer to the [PgBouncer documentation](https://www.pgbouncer.org/features.html) to check other limitations of chosen pool mode.
 
 
 ## Next steps