Fixing bad merge conflict resolution

Author: ShannonLeavitt

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

@@ -62,45 +62,6 @@ If in-place major version upgrade pre-check operations fail, then the upgrade ab
 -	Servers configured with logical replication slots aren't supported. 
 
 - In-place major version upgrade doesn't yet support upgrading to version 16, our team is actively working on this feature.
-
-## How to perform in-place major version upgrade: 
-
-It's recommended to perform a dry run of the in-place major version upgrade in a non-production environment before upgrading the production server. It allows you to identify any application incompatibilities and validate that the upgrade completes successfully before upgrading the production environment. You can perform a Point-In-Time Recovery (PITR) of your production server, and restore it in the non-production environment to test the upgrade there. Addressing these issues before the production upgrade minimizes downtime and ensures a smooth upgrade process. 
-
-**Steps**
-
-1. You can perform in-place major version upgrade using Azure portal or CLI (command-line interface).  Click the **Upgrade** button in Overview blade.
-
-   :::image type="content" source="media/concepts-major-version-upgrade/upgrade-tab.png" alt-text="Diagram of Upgrade tab to perform in-place major version upgrade.":::
-
-2. You'll see an option to select the major version of your choice, you have an option to skip versions to directly upgrade to higher versions. Choose the version and click **Upgrade**. 
-
-   :::image type="content" source="media/concepts-major-version-upgrade/set-postgresql-version.png" alt-text="Diagram of PostgreSQL version to Upgrade.":::
-
-3. During upgrade, users have to wait for the process to complete. You can resume accessing the server once the server is back online. 
-
-   :::image type="content" source="media/concepts-major-version-upgrade/deployment-progress.png" alt-text="Diagram of deployment progress for major version upgrade.":::
-
-4. Once the upgrade is successful, you can expand the **Deployment details** tab and click **Operation details**  to see more information about upgrade process like duration, provisioning state etc. 
-
-   :::image type="content" source="media/concepts-major-version-upgrade/deployment-success.png" alt-text="Diagram of successful deployment of for major version upgrade.":::
-
-5. You can click on the **Go to resource** tab to validate your upgrade. Notice that server name remained unchanged and PostgreSQL version upgraded to desired higher version with the latest minor version. 
-
-   :::image type="content" source="media/concepts-major-version-upgrade/upgrade-verification.png" alt-text="Diagram of Upgraded version to Flexible Server after major version upgrade.":::
-
-
-## Post upgrade
-
-Run the **ANALYZE** operation to refresh the `pg_statistic` table. You should do this for every database on all your Azure Database for PostgreSQL flexible server instances. Optimizer statistics aren't transferred during a major version upgrade, so you need to regenerate all statistics to avoid performance issues. Run the command without any parameters to generate statistics for all regular tables in the current database, as follows:
-
-```
-VACUUM ANALYZE VERBOSE;
-```
-> [!NOTE]   
->
-> The VERBOSE flag is optional, but using it shows you the progress. 
-
 
 ## Next steps