General improvement public doc updates

Author: VandhanaMehta

articles/mysql/flexible-server/concepts-business-continuity.md

@@ -54,6 +54,11 @@ Here are some unplanned failure scenarios and the recovery process:
 | **Availability zone failure** | While it's a rare event, if you want to recover from a zone-level failure, you can perform Geo restore from to a paired region. RPO would be <1 h and RTO would vary. <br /> <br /> You can also use [read replica](./concepts-read-replicas.md) as DR solution by creating replica in other availability zone. RTO\RPO is like what is detailed above. | If you have enabled Zone redundant HA, Flexible server performs automatic failover to the standby site. Refer to [HA concepts](./concepts-high-availability.md) for more details. RTO is expected to be 60-120 s, with RPO=0.<br /> <br />Other available options are restored from backup. You can use both PITR or Geo restore from paired region.<br />**PITR :** RTO: Varies, RPO=0 sec <br />**Geo Restore :** RTO: Varies, RPO <1 h <br /> <br /> **Note:** *If you have same zone HA enabled the options are same as what we have for Recovery process [non-HA]* |
 | **Region failure** |While it's a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. A new flexible server will be deployed to the selected region. The time taken to restore depends on the previous backup and the number of transaction logs to recover.  RPO in most cases would be <1 h and RTO would vary.  | For this scenario, the options are same as for Recovery process [non-HA] . |
 
+## Requirements and Limitations
+
+**Region Data Residency**
+
+By default, Azure Database for MySQL - Flexible Server doesn't move or store customer data out of the region it is deployed in. However, customers can optionally chose to enable geo-redundant backups or set up cross-region replication for storing data in another region.
 
 ## Next steps
 

articles/mysql/flexible-server/concepts-read-replicas.md

@@ -76,7 +76,7 @@ Azure Database for MySQL Flexible Server provides the **Replication lag in secon
 If you see increased replication lag, refer to [troubleshooting replication latency](./../howto-troubleshoot-replication-latency.md) to troubleshoot and understand possible causes.
 
 >[!IMPORTANT]
->Read Replica on HA server uses storage based replication technology, which no longer uses 'SLAVE_IO_RUNNING' metric available in MySQL's 'SHOW SLAVE STATUS' command. The value of it will always be displayed as "No" and is not indicative of replication status.
+>Read Replica on HA server uses storage based replication technology, which no longer uses 'SLAVE_IO_RUNNING' metric available in MySQL's 'SHOW SLAVE STATUS' command. The value of it will always be displayed as "No" and is not indicative of replication status. To know the correct status of replication, please refer to replication metrics - **Replica IO Status** and **Replica SQL Status** under monitoring blade. 
 
 ## Stop replication
 

articles/mysql/flexible-server/how-to-data-in-replication.md

@@ -231,7 +231,9 @@ The following steps prepare and configure the MySQL server hosted on-premises, i
    show slave status;
    ```
 
-   If the state of `Slave_IO_Running` and `Slave_SQL_Running` are "yes" and the value of `Seconds_Behind_Master` is "0", replication is working well. `Seconds_Behind_Master` indicates how late the replica is. If the value isn't "0", it means that the replica is processing updates.
+  To know the correct status of replication, please refer to replication metrics - **Replica IO Status** and **Replica SQL Status** under monitoring blade. 
+  
+  If the `Seconds_Behind_Master` is "0", replication is working well. `Seconds_Behind_Master` indicates how late the replica is. If the value isn't "0", it means that the replica is processing updates. 
 
 ## Other useful stored procedures for Data-in replication operations