Fixing blockers for merge

Author: v-regandowner

articles/postgresql/flexible-server/concepts-major-version-upgrade.md

@@ -7,6 +7,7 @@ ms.reviewer: rajsell
 ms.date: 02/08/2023
 ms.service: postgresql
 ms.subservice: flexible-server
+ms.custom: references_regions
 ms.topic: conceptual
 ---
 
@@ -25,42 +26,42 @@ Azure Database for PostgreSQL Flexible Server Postgres has now introduced in-pla
 
 Here are some of the important considerations with in-place major version upgrade. 
 
-•	During in-place major version upgrade process,  Flexible Server runs a pre-check procedure to identify any potential issues that might cause the upgrade to fail. If the pre-check finds any incompatibilities, it creates a log event showing that the upgrade pre-check failed, along with an error message. 
+- During in-place major version upgrade process,  Flexible Server runs a pre-check procedure to identify any potential issues that might cause the upgrade to fail. If the pre-check finds any incompatibilities, it creates a log event showing that the upgrade pre-check failed, along with an error message. 
 
-•	If the pre-check is successful, then Flexible Server stops the service and takes an implicit backup just before starting the upgrade. This backup can be used to restore the database instance to its previous version if there's an upgrade error. 
+- If the pre-check is successful, then Flexible Server stops the service and takes an implicit backup just before starting the upgrade. This backup can be used to restore the database instance to its previous version if there's an upgrade error. 
 
-•	Flexible Server uses  **pg_upgrade** utility to perform in-place major version upgrades and  provides the flexibility to skip versions and upgrade directly to higher versions. 
+- Flexible Server uses  **pg_upgrade** utility to perform in-place major version upgrades and  provides the flexibility to skip versions and upgrade directly to higher versions. 
 
-•	During an in-place major version upgrade of a High Availability (HA) enabled server, the service disables HA, performs the upgrade on the primary server, and then re-enables HA after the upgrade is complete. 
+-	During an in-place major version upgrade of a High Availability (HA) enabled server, the service disables HA, performs the upgrade on the primary server, and then re-enables HA after the upgrade is complete. 
 
-•	Most extensions are automatically upgraded to higher versions during an in-place major version upgrade, with some exceptions. Refer **limitations** section for more details. 
+-	Most extensions are automatically upgraded to higher versions during an in-place major version upgrade, with some exceptions. Refer **limitations** section for more details. 
 
-•	In-place major version upgrade process for Flexible server automatically deploys the latest supported minor version. 
+-	In-place major version upgrade process for Flexible server automatically deploys the latest supported minor version. 
 
-•	In-place major version upgrade process is an offline operation and it involves a short downtime.  
+-	In-place major version upgrade process is an offline operation and it involves a short downtime.  
 
-•	Long-running transactions or high workload before the upgrade might increase the time taken to shut down the database and increase upgrade time. 
+-	Long-running transactions or high workload before the upgrade might increase the time taken to shut down the database and increase upgrade time. 
 
-•	If an in-place major version upgrade fails, the service restores the server to its previous state using a backup taken as part of step 2.
+-	If an in-place major version upgrade fails, the service restores the server to its previous state using a backup taken as part of step 2.
 
-•	Once the in-place major version upgrade is successful, there are no automated ways to revert to the earlier version. However, you can perform a Point-In-Time Recovery (PITR) to a time prior to the upgrade to restore the previous version of the database instance.
+-	Once the in-place major version upgrade is successful, there are no automated ways to revert to the earlier version. However, you can perform a Point-In-Time Recovery (PITR) to a time prior to the upgrade to restore the previous version of the database instance.
 
 ## Limitations:  
 
 During preview, if in-place major version upgrade pre-check operations fail then it aborts with a detailed error message for all the below limitations.
 
-•	In-place major version upgrade currently doesn't support read replicas, so if you have a read replica enabled server, you need to delete the replica before performing the upgrade on the primary server. After the upgrade, you can recreate the replica. 
+- In-place major version upgrade currently doesn't support read replicas, so if you have a read replica enabled server, you need to delete the replica before performing the upgrade on the primary server. After the upgrade, you can recreate the replica. 
 
-•	In-place major version upgrade doesn't support certain extensions and there are some limitations to upgrading certain extensions. The extensions **Timescaledb**, **pgaudit**, **dblink**, and **postgres_fdw** are unsupported for all PostgreSQL versions during preview. 
+- In-place major version upgrade doesn't support certain extensions and there are some limitations to upgrading certain extensions. The extensions **Timescaledb**, **pgaudit**, **dblink**, and **postgres_fdw** are unsupported for all PostgreSQL versions during preview. 
 
-•	Upgrading the **PostGIS** extension is currently unsupported from PostgreSQL 12, while upgrading the **orafce** extension is unsupported from PostgreSQL 11. All other versions of these extensions are supported for in-place major version upgrade. 
+-	Upgrading the **PostGIS** extension is currently unsupported from PostgreSQL 12, while upgrading the **orafce** extension is unsupported from PostgreSQL 11. All other versions of these extensions are supported for in-place major version upgrade. 
 
-•	During preview, in-place major version upgrade is currently available in the following regions.  
+-	During preview, in-place major version upgrade is currently available in the following regions.  
   Australia East / Australia Southeast/ Canada East/ China North 3/China East 3/ East Asia / East US / France South / India Central / India South /Japan East /Jio India West /Korea Central / Norway East/ North Europe/South Central US /Sweden Central /Switzerland North /Switzerland West /UAE north /West Central US/ West US / West US3/ Qatar  Central
 
-•	Servers configured with logical replication slots aren't supported. 
+-	Servers configured with logical replication slots aren't supported. 
 
-•	MVU is currently not supported for PgBouncer enabled servers.
+-	MVU is currently not supported for PgBouncer enabled servers.
 
 
 ## How to Perform in-place major version upgrade: 
@@ -132,7 +133,7 @@ Run the **ANALYZE** operation to refresh the pg_statistic table. You should do t
 ANALYZE VERBOSE
 ```
 > [!NOTE]   
-
+>
 > The VERBOSE flag is optional, but using it shows you the progress. 
 
 ## Next steps