update

Author: rachel-msft

articles/postgresql/concepts-audit.md

@@ -80,7 +80,7 @@ To learn more about `log_line_prefix`, visit the [PostgreSQL documentation](http
 ### Getting started
 To quickly get started, set `pgaudit.log` to `WRITE`, and open your logs to review the output. 
 
-### Viewing audit logs
+## Viewing audit logs
 If you are using .log files, your audit logs will be included in the same file as your PostgreSQL error logs. You can download log files from the Azure [portal](howto-configure-server-logs-in-portal.md) or [CLI](howto-configure-server-logs-using-cli.md). 
 
 If you are using Azure diagnostic logging, the way you access the logs depends on which endpoint you choose. For Azure Storage, see the [logs storage account](../azure-monitor/platform/resource-logs-collect-storage.md) article. For Event Hubs, see the [stream Azure logs](../azure-monitor/platform/resource-logs-stream-event-hubs.md) article.

articles/postgresql/concepts-limits.md

@@ -37,7 +37,7 @@ When connections exceed the limit, you may receive the following error:
 > [!IMPORTANT]
 > For best experience, we recommend that you use a connection pooler like pgBouncer to efficiently manage connections.
 
-A PostgreSQL connection, even idle, can occupy about 10MB of memory. Also, creating new connections takes time. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that avoids idle connections and reuses existing connections will help address this. To learn more, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/not-all-postgres-connection-pooling-is-equal/ba-p/825717).
+A PostgreSQL connection, even idle, can occupy about 10MB of memory. Also, creating new connections takes time. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn more, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/not-all-postgres-connection-pooling-is-equal/ba-p/825717).
 
 ## Functional limitations
 ### Scale operations