Merge pull request #232715 from varun-dhawan/varund-novena

[PostgreSQL] updates the section heading

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-query-store.md

@@ -22,15 +22,17 @@ Query Store is an opt-in feature, so it isn't enabled by default on a server. Qu
 > Do not enable Query Store on Burstable pricing tier as it would cause performance impact.
 
 
-### Enable Query Store using the Azure portal
+### Enable Query Store
 1. Sign in to the Azure portal and select your Azure Database for PostgreSQL server.
 2. Select **Server Parameters** in the **Settings** section of the menu.
 3. Search for the `pg_qs.query_capture_mode` parameter.
 4. Set the value to `TOP` or `ALL` and **Save**.
 Allow up to 20 minutes for the first batch of data to persist in the azure_sys database.
-To enable wait statistics in your Query Store:
+
+### Enable Query Store Wait Sampling
 1. Search for the `pgms_wait_sampling.query_capture_mode` parameter.
 2. Set the value to `ALL` and **Save**.
+
 ## Information in Query Store
 Query Store has two stores:
 - A runtime stats store for persisting the query execution statistics information.
@@ -165,7 +167,8 @@ This view returns the query plan that was used to execute a query. There is one
 `staging_data_reset` discards all statistics gathered in memory by Query Store (that is, the data in memory that has not been flushed yet to the database). This function can only be executed by the server admin role.
 
 ## Limitations and known issues
-- If a PostgreSQL server has the parameter default_transaction_read_only on, Query Store will not capture any data.
+- If a PostgreSQL server has the parameter `default_transaction_read_only` on, Query Store will not capture any data.
+- 
 ## Next steps
 - Learn more about [scenarios where Query Store can be especially helpful](concepts-query-store-scenarios.md).
 - Learn more about [best practices for using Query Store](concepts-query-store-best-practices.md).