Updated bookmarks and section name

Author: hariramt

articles/mysql/concepts-version-policy.md

@@ -103,7 +103,7 @@ A: Azure Database for MySQL enables you to carry out in-place major version upgr
 
 __Q: Are there any expected downtime or performance impacts during a major version upgrade?__
 
-A: Yes, there's some downtime during the major version upgrade process. The specific duration varies depending on factors such as the size and complexity of the database. We recommend conducting a test upgrade in a nonproduction environment to assess the expected downtime and evaluate potential performance. To minimize downtime for your applications during the upgrade, you can explore the [recommended major version upgrade procedure across major versions using Read replica or Point-in-time restore (PITR)](flexible-server/how-to-upgrade.md#recommended-major-version-upgrade-procedure-across-major-versions-using-read-replica-or-point-in-time-restore-pitr).
+A: Yes, there's some downtime during the major version upgrade process. The specific duration varies depending on factors such as the size and complexity of the database. We recommend conducting a test upgrade in a nonproduction environment to assess the expected downtime and evaluate potential performance. To minimize downtime for your applications during the upgrade, you can explore the [recommended major version upgrade procedure across major versions](flexible-server/how-to-upgrade.md#recommended-major-version-upgrade-procedure-across-major-versions).
 
 __Q: Can I roll back to a previous major version after upgrading?__
 

articles/mysql/flexible-server/how-to-upgrade-faq.md

@@ -19,7 +19,7 @@ ai-usage: ai-assisted
 
 - Q: **Will this cause downtime of the server, and if so, how long?**
 
-    A. To have minimal downtime during upgrades, follow the steps mentioned under [Recommended major version upgrade procedure across major versions using Read replica or Point-in-time restore (PITR)](flexible-server/how-to-upgrade.md#recommended-major-version-upgrade-procedure-across-major-versions-using-read-replica-or-point-in-time-restore-pitr). The server is unavailable during the upgrade process, so we recommend you perform this operation during your planned maintenance window. The estimated downtime depends on the database size, storage size provisioned (IOPs provisioned), and the number of tables on the database. The upgrade time is directly proportional to the number of tables on the server. To estimate the downtime for your server environment, we recommend first performing an upgrade on a restored copy of the server.
+    A. To have minimal downtime during upgrades, follow the steps mentioned under [Recommended major version upgrade procedure across major versions](flexible-server/how-to-upgrade.md#recommended-major-version-upgrade-procedure-across-major-versions). The server is unavailable during the upgrade process, so we recommend you perform this operation during your planned maintenance window. The estimated downtime depends on the database size, storage size provisioned (IOPs provisioned), and the number of tables on the database. The upgrade time is directly proportional to the number of tables on the server. To estimate the downtime for your server environment, we recommend first performing an upgrade on a restored copy of the server.
 
 - Q: **I'm using an HA server. Can I expect a near zero downtime experience for a major version upgrade, similar to routine maintenance?**
 

articles/mysql/flexible-server/how-to-upgrade.md

@@ -171,7 +171,7 @@ To perform a major version upgrade of an Azure Database for MySQL Flexible Serve
 
 1. Go to your primary server and perform a major version upgrade.
 
-## Recommended major version upgrade procedure across major versions using Read replica or Point-in-time restore (PITR)
+## Recommended major version upgrade procedure across major versions
 
 To perform a major version upgrade of an Azure Database for MySQL Flexible Server with minimal downtime using read replica servers or PITR, perform the following steps.