modifying files for general correctness

Author: VandhanaMehta

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

@@ -45,6 +45,11 @@ Because replicas are read-only, they don't directly reduce write-capacity burden
 
 The read replica feature uses MySQL asynchronous replication. The feature isn't meant for synchronous replication scenarios. There's a measurable delay between the source and the replica. The data on the replica eventually becomes consistent with the data on the source. Use this feature for workloads that can accommodate this delay.
 
+## Cross-region replication
+
+You can create a read replica in a different region from your source server. Cross-region replication can be helpful for scenarios like disaster recovery planning or bringing data closer to your users. Azure database for MySQL Flexible Server allows you to provision read-replica in the Azure supported geo-paired region to the source server. Learn more about Azure Paired Regions [here](https://learn.microsoft.com/azure/reliability/cross-region-replication-azure).
+
+
 ## Create a replica
 
 If a source server has no existing replica servers, the source first restarts to prepare itself for replication.

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

@@ -215,14 +215,14 @@ The results should appear similar to the following. Make sure to note the binary
 
    All Data-in replication functions are done by stored procedures. You can find all procedures at [Data-in replication Stored Procedures](../reference-stored-procedures.md). The stored procedures can be run in the MySQL shell or MySQL Workbench.
 
-To link two servers and start replication, login to the target replica server in the Azure Database for MySQL service and set the external instance as the source server. This is done by using the `mysql.az_replication_change_master` stored procedure on the Azure Database for MySQL server.
+To link two servers and start replication, login to the target replica server in the Azure Database for MySQL service and set the external instance as the source server. This is done by using the `mysql.az_replication_change_master` or `mysql.az_replication_change_master_with_gtid` stored procedure on the Azure Database for MySQL server.
 
    ```sql
    CALL mysql.az_replication_change_master('<master_host>', '<master_user>', '<master_password>', <master_port>, '<master_log_file>', <master_log_pos>, '<master_ssl_ca>');
    ```
 
    ```sql
-   CALL mysql.az_replication_change_master_with_gtid('<master_host>', '<master_user>', '<master_password>', <master_port>, '<master_log_file>', <master_log_pos>, '<master_ssl_ca>');
+   CALL mysql.az_replication_change_master_with_gtid('<master_host>', '<master_user>', '<master_password>', <master_port>,'<master_ssl_ca>');
    ```
 
    - master_host: hostname of the source server
@@ -256,6 +256,9 @@ To link two servers and start replication, login to the target replica server in
    ```sql
    CALL mysql.az_replication_change_master('master.companya.com', 'syncuser', 'P@ssword!', 3306, 'mysql-bin.000002', 120, @cert);
    ```
+   ```sql
+   CALL mysql.az_replication_change_master_with_gtid('master.companya.com', 'syncuser', 'P@ssword!', 3306, @cert);
+   ```
 
    *Replication without SSL*
 
@@ -264,6 +267,9 @@ To link two servers and start replication, login to the target replica server in
    ```sql
    CALL mysql.az_replication_change_master('master.companya.com', 'syncuser', 'P@ssword!', 3306, 'mysql-bin.000002', 120, '');
    ```
+   ```sql
+   CALL mysql.az_replication_change_master_with_gtid('master.companya.com', 'syncuser', 'P@ssword!', 3306, '');
+   ```
 
 1. Start replication.
 

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

@@ -155,7 +155,7 @@ Restore the dump file to the server created in the Azure Database for MySQL - Fl
    SOURCE_HOST='<master_host>',
    SOURCE_USER='<master_user>',
    SOURCE_PASSWORD='<master_password>',
-   SOURCE_LOG_FILE='<master_log_file>,
+   SOURCE_LOG_FILE='<master_log_file>',
    SOURCE_LOG_POS=<master_log_pos>
    ```