Merge pull request #215011 from VandhanaMehta/generaldoccorrections

Adding general public doc corrections

Author: prmerger-automator[bot]

articles/mysql/flexible-server/concepts-high-availability.md

@@ -115,7 +115,6 @@ Here are some considerations to keep in mind when you use high availability:
 * Zone-redundant high availability can be set only when the flexible server is created.
 * High availability isn't supported in the burstable compute tier.
 * Restarting the primary database server to pick up static parameter changes also restarts the standby replica.
-* Read replicas aren't supported for HA servers.
 * Data-in Replication isn't supported for HA servers.
 * GTID mode will be turned on as the HA solution uses GTID. Check whether your workload has [restrictions or limitations on replication with GTIDs](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html).  
 >[!Note] 

articles/mysql/flexible-server/concepts-limitations.md

@@ -71,15 +71,11 @@ The following are unsupported:
 ### Scale operations
 - Decreasing server storage provisioned is not supported.
 
-### Read replicas
-- Not supported with zone redundant HA configurations (both primary and standby).
-
 ### Server version upgrades
 - Automated migration between major database engine versions is not supported. If you would like to upgrade the major version, take a [dump and restore](../concepts-migrate-dump-restore.md) it to a server that was created with the new engine version.
 
 ### Restoring a server
 - With point-in-time restore, new servers are created with the same compute and storage configurations as the source server it is based on. The newly restored server's compute can be scaled down after the server is created.
-- Restoring a deleted server isn't supported.
 
 ## Features available in Single Server but not yet supported in Flexible Server
 Not all features available in Azure Database for MySQL - Single Server is available in Flexible Server yet. For complete list of feature comparison between single server and flexible server, refer [choosing the right MySQL Server option in Azure documentation.](../select-right-deployment-type.md#comparing-the-mysql-deployment-options-in-azure)

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

@@ -80,7 +80,7 @@ The main differences between these options are listed in the following table:
 | Gtid support for read replicas | Supported | Supported | User Managed |
 | Cross-region support (Geo-replication) | Yes | Not supported | User Managed |
 | Hybrid scenarios | Supported with [Data-in Replication](./concepts-data-in-replication.md)| Supported with [Data-in Replication](../flexible-server/concepts-data-in-replication.md) | User Managed |
-| Gtid support for data-in replication | Supported | Supported | User Managed |
+| Gtid support for data-in replication | Supported | Not Supported | User Managed |
 | Data-out replication | Not Supported | In preview | Supported |
 | [**Backup and Recovery**](../flexible-server/concepts-backup-restore.md) | | | |
 | Automated backups | Yes | Yes | No |