Merge pull request #102845 from NavtejSaini-MSFT/patch-40

Fixes https://github.com/MicrosoftDocs/azure-docs/issues/47156

Author: PRMerger7

articles/mysql/select-right-deployment-type.md

@@ -31,7 +31,7 @@ The main differences between these options are listed in the following table:
 | Service-level agreement (SLA)                | Offers SLA of 99.99% availability| Up to 99.95% availability with two or more instances in the same availability set.<br/><br/>99.9% availability with a single instance VM using premium storage.<br/><br/>99.99% using Availability Zones with multiple instances in multiple availability sets.<br/><br/>See the [Virtual Machines SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/v1_8/). |
 | Operating system patching        | Automatic  | Managed by customers |
 | MySQL patching     | Automatic  | Managed by customers |
-| High availability | The high availability (HA) model is based on built-in failover mechanisms for when a node-level interruption occurs. In such cases, the service automatically creates a new instance and attaches storage to this instance. | Customers architect, implement, test, and maintain high availability. Capabilities might include always-on failover clustering, always-on group replication, log shipping, or transactional replication.|
+| High availability | The high availability (HA) model is based on built-in failover mechanisms for when a node-level interruption occurs. In such cases, the service automatically creates a new instance and attaches storage to this instance. | Customers architect, implement, test, and maintain high availability. Capabilities might include clustering,replication etc.|
 | Zone redundancy | Currently not supported | Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center.|
 | Hybrid scenarios | With [Data-in Replication](https://docs.microsoft.com/azure/mysql/concepts-data-in-replication), you can synchronize data from an external MySQL server into the Azure Database for MySQL service. The external server can be on-premises, in virtual machines, or a database service hosted by other cloud providers.<br/><br/> With the [read replica](https://docs.microsoft.com/azure/mysql/concepts-read-replicas) feature, you can replicate data from an Azure Database for MySQL master server to up to five read-only replica servers. The replicas are either within the same Azure region or across regions. Read-only replicas are asynchronously updated using binlog replication technology.| Managed by customers
 | Backup and restoration | Automatically creates [server backups](https://docs.microsoft.com/azure/mysql/concepts-backup#backups) and stores them in user-configured storage that is either locally redundant or geo-redundant. The service takes full, differential, and transaction log backups | Managed by customers |