Merge pull request #112230 from hyoshioka0128/patch-686

Typo "MySQL Flexible server"→"MySQL Flexible Server"

Author: Court72

articles/reliability/migrate-database-mysql-flex.md

@@ -15,7 +15,7 @@ ms.custom: references_regions, subject-reliability
 
 This guide describes how to migrate MySQL – Flexible Server from non-availability zone support to availability zone support.
 
-You can configure Azure Database for MySQL Flexible server to use one of two high availability (HA) architectural models:
+You can configure Azure Database for MySQL Flexible Server to use one of two high availability (HA) architectural models:
 
 - **Same-zone HA architecture (zonal).** This option is preferred for infrastructure redundancy with lower network latency because the primary and standby servers will be in the same availability zone. It provides high availability without the need to configure application redundancy across zones. Same-zone HA is preferred when you want to achieve the highest level of availability within a single availability zone with the lowest network latency. Same-zone HA is available in all Azure regions where you can use Azure Database for MySQL - Flexible Server. To learn more about same-zone HA architecture, see [Same-zone HA architecture](../mysql/flexible-server/concepts-high-availability.md#same-zone-ha-architecture).
 
@@ -39,12 +39,12 @@ To migrate your existing workload from zonal (same-zone HA) to zone-redundant HA
      - An Azure Database for MySQL Flexible Server that wasn't enabled for HA at the time of create.  
 
     >[!IMPORTANT]
-    > If you've originally provisioned your Azure Database for MySQL Flexible server as a non-HA server, you can simply enable it for same-zone HA architecture. However, if you want to enable it for zone-redundant HA architecture, then you'll need to implement one of the available migration options listed in this article.
+    > If you've originally provisioned your Azure Database for MySQL Flexible Server as a non-HA server, you can simply enable it for same-zone HA architecture. However, if you want to enable it for zone-redundant HA architecture, then you'll need to implement one of the available migration options listed in this article.
     
-2.	You'll need to create a target server that's running Azure Database for MySQL Flexible Server [in a region that supports availability zones](../mysql/flexible-server/overview.md#azure-regions). For more information on how to create an Azure Database for MySQL flexible server, see [Use the Azure portal to create an Azure Database for MySQL flexible server](../mysql/flexible-server/quickstart-create-server-portal.md). Make sure that the created server is configured for zone redundancy by enabling HA and selecting the *Zone-Redundant* option.
+2.	You'll need to create a target server that's running Azure Database for MySQL Flexible Server [in a region that supports availability zones](../mysql/flexible-server/overview.md#azure-regions). For more information on how to create an Azure Database for MySQL Flexible Server, see [Use the Azure portal to create an Azure Database for MySQL Flexible Server](../mysql/flexible-server/quickstart-create-server-portal.md). Make sure that the created server is configured for zone redundancy by enabling HA and selecting the *Zone-Redundant* option.
 
 >[!TIP]
-> If you want the flexibility of being able to move between zonal (same-zone) and zone-redundant HA in the future, you can provision your Azure Database for MySQL Flexible server with zone-redundant HA enabled during server create. Once the server is provisioned, you can then disable HA.
+> If you want the flexibility of being able to move between zonal (same-zone) and zone-redundant HA in the future, you can provision your Azure Database for MySQL Flexible Server with zone-redundant HA enabled during server create. Once the server is provisioned, you can then disable HA.
 
 
 
@@ -58,17 +58,17 @@ Migrations can be categorized as either online or offline:
 
 ## Migration Option 1: Offline Migration
 
-You can migrate from one Azure Database for Flexible server to another by using one of the following tools. Both of these options will require downtime.
+You can migrate from one Azure Database for Flexible Server to another by using one of the following tools. Both of these options will require downtime.
 
-1. **Data Migration Service (DMS).** To learn how to migrate MySQL Flexible Server to another with DMS, see [Migrate Azure Database for MySQL - Single Server to Flexible Server offline using DMS via the Azure portal](../dms/tutorial-mysql-azure-single-to-flex-offline-portal.md). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible server that doesn’t support availability zones to another that supports availability zones.
+1. **Data Migration Service (DMS).** To learn how to migrate MySQL Flexible Server to another with DMS, see [Migrate Azure Database for MySQL - Single Server to Flexible Server offline using DMS via the Azure portal](../dms/tutorial-mysql-azure-single-to-flex-offline-portal.md). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible Server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible Server that doesn’t support availability zones to another that supports availability zones.
 
-2. **Open-source tools**. You can migrate offline with open-source tools, such as **MySQL Workbench**, **mydumper/myloader**, or **mysqldump** to backup and restore the database. For information on how to use these tools, see [Options for migrating Azure Database for  MySQL - Single Server to Flexible Server](https://techcommunity.microsoft.com/t5/azure-database-for-mysql-blog/options-for-migrating-azure-database-for-mysql-single-server-to/ba-p/2674062). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible server that doesn’t support availability zones to another that supports availability zones.
+2. **Open-source tools**. You can migrate offline with open-source tools, such as **MySQL Workbench**, **mydumper/myloader**, or **mysqldump** to backup and restore the database. For information on how to use these tools, see [Options for migrating Azure Database for  MySQL - Single Server to Flexible Server](https://techcommunity.microsoft.com/t5/azure-database-for-mysql-blog/options-for-migrating-azure-database-for-mysql-single-server-to/ba-p/2674062). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible Server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible Server that doesn’t support availability zones to another that supports availability zones.
 
 ## Migration Option 2: Online Migration
 
-You can migrate from one Azure Database for Flexible server to another with minimum downtime to your applications by using one of the following tools:
+You can migrate from one Azure Database for Flexible Server to another with minimum downtime to your applications by using one of the following tools:
 
-1. **Data Migration Service (DMS).** To learn how to migrate MySQL Flexible Server to another with DMS, see [Migrate Azure Database for MySQL - Single Server to Flexible Server online using DMS via the Azure portal](../dms/tutorial-mysql-azure-single-to-flex-online-portal.md). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible server that doesn’t support availability zones to another that supports availability zones.
+1. **Data Migration Service (DMS).** To learn how to migrate MySQL Flexible Server to another with DMS, see [Migrate Azure Database for MySQL - Single Server to Flexible Server online using DMS via the Azure portal](../dms/tutorial-mysql-azure-single-to-flex-online-portal.md). Although the tutorial outlines steps for migrating from Azure MySQL Single Server to Flexible Server, you can use the same procedure for migrating data from one Azure Database for MySQL Flexible Server that doesn’t support availability zones to another that supports availability zones.
 
 2. **Open-source tools.** You can use a combination of open-source tools such as **mydumper/myloader** together with **Data-in replication**. To learn how to set up Data-in Replication, see [How to configure Azure Database for MySQL Data-in Replication](../mysql/single-server/how-to-data-in-replication.md).