Corrections for Server Parameters

Author: aditiiitb

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

@@ -108,7 +108,7 @@ After your application is successfully processing reads and writes, you have com
 
 ## Global transaction identifier (GTID)
 
-Global transaction identifier (GTID) is a unique identifier created with each committed transaction on a source server and is OFF by default in Azure Database for MySQL Flexible serever. GTID is supported on versions 5.7 and 8.0. To learn more about GTID and how it's used in replication, refer to MySQL's [replication with GTID](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html) documentation.
+Global transaction identifier (GTID) is a unique identifier created with each committed transaction on a source server and is OFF by default in Azure Database for MySQL Flexible server. GTID is supported on versions 5.7 and 8.0. To learn more about GTID and how it's used in replication, refer to MySQL's [replication with GTID](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html) documentation.
 
 The following server parameters are available for configuring GTID:
 

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

@@ -70,12 +70,12 @@ Azure Database for MySQL Flexible Server supports at largest, **4 TB**, in a sin
 
 ### innodb_log_file_size
 
-(innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] is the size in bytes of each (log file)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_file] in a (log group)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_group]. The combined size of log files ((innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] * (innodb_log_files_in_group)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_files_in_group]) cannot exceed a maximum value that is slightly less than 512GB.). A bigger log file size is better for performance, but it has a drawback that the recovery time after a crash will be high. You need to balance recovery time in the rare event of a crash recovery versus maximizing throughput during peak operations. These can also result in longer restart times. You can configure innodb_log_size to any of these values - 256MB, 512MB, 1GB or 2GB for Azure database for MySQL Flexible server. The parameter is static and requires a restart.
+[innodb_log_file_size](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size) is the size in bytes of each [log file](https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_file) in a [log group](https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_group). The combined size of log files [(innodb_log_file_size](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size) * [innodb_log_files_in_group](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_files_in_group)) cannot exceed a maximum value that is slightly less than 512GB). A bigger log file size is better for performance, but it has a drawback that the recovery time after a crash will be high. You need to balance recovery time in the rare event of a crash recovery versus maximizing throughput during peak operations. These can also result in longer restart times. You can configure innodb_log_size to any of these values - 256MB, 512MB, 1GB or 2GB for Azure database for MySQL Flexible server. The parameter is static and requires a restart.
 
 > [!NOTE]
-> If you have changed the parameter innodb_log_file_size from default, please check if the value of "show global status like 'innodb_buffer_pool_pages_dirty'", stays at 0 for 30 sec ” to avoid restart delay.
+> If you have changed the parameter innodb_log_file_size from default, check if the value of "show global status like 'innodb_buffer_pool_pages_dirty'" stays at 0 for 30 seconds to avoid restart delay.
+
 
- 
 
 ### max_connections
 

articles/mysql/flexible-server/connect-azure-cli.md

@@ -21,10 +21,10 @@ This quickstart demonstrates how to connect to an Azure Database for MySQL Flexi
 
     [!INCLUDE [flexible-server-free-trial-note](../includes/flexible-server-free-trial-note.md)]
 - Install [Azure CLI](/cli/azure/install-azure-cli) latest version (2.20.0 or above)
-- Login using Azure CLI with ```az login``` command
+- Log in using Azure CLI with ```az login``` command
 - Turn on parameter persistence with ```az config param-persist on```. Parameter persistence will help you use local context without having to repeat a lot of arguments like resource group or location etc.
 
-## Create an MySQL Flexible Server
+## Create a MySQL Flexible Server
 
 The first thing we'll create is a managed MySQL server. In [Azure Cloud Shell](https://shell.azure.com/), run the following script and make a note of the **server name**, **username** and  **password** generated from this command.
 
@@ -69,9 +69,9 @@ Successfully connected to mysqldemoserver1.
 ```
 If the connection failed, try these solutions:
 - Check if port 3306 is open on your client machine.
-- if your server administrator user name and password are correct
-- if you have configured firewall rule for your client machine
-- if you have configured your server with private access in virtual networking, make sure your client machine is in the same virtual network.
+- If your server administrator user name and password are correct
+- If you have configured firewall rule for your client machine
+- If you have configured your server with private access in virtual networking, make sure your client machine is in the same virtual network.
 
 ## Run multiple queries using interactive mode
 You can run multiple queries using the **interactive** mode. To enable interactive mode, run the following command

articles/mysql/flexible-server/how-to-read-replicas-cli.md

@@ -5,7 +5,7 @@ author: savjani
 ms.author: pariks
 ms.service: mysql
 ms.topic: how-to
-ms.date: 10/23/2020
+ms.date: 10/23/2021
 ms.custom: devx-track-azurecli
 ---
 

articles/mysql/flexible-server/quickstart-create-server-cli.md

@@ -12,7 +12,7 @@ ms.custom: mvc, devx-track-azurecli
 
 # Quickstart: Create an Azure Database for MySQL Flexible Server using Azure CLI
 
-[[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
+[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
 
 This quickstart shows how to use the [Azure CLI](/cli/azure/get-started-with-azure-cli) commands in [Azure Cloud Shell](https://shell.azure.com) to create an Azure Database for MySQL Flexible Server in five minutes. 

articles/mysql/flexible-server/whats-new.md

@@ -51,9 +51,7 @@ This article summarizes new releases and features in Azure Database for MySQL -
 
 - **Static Parameter innodb_log_file_size is now Configurable**
 
-    [innodb_log_file_size](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size) can be configured now to any of these value 256MB,512MB,1GB or 2GB. As this is a static parameter it will require a server restart. 
-    
-    If you have changed the parameter innodb_log_file_size from default, please check if the value of "show global status like 'innodb_buffer_pool_pages_dirty'", stays at 0 for 30 sec ” to avoid restart delay. [Learn More](./concepts-server-parameters.md) 
+    [innodb_log_file_size](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size) can now be configured to any of these values: 256MB, 512MB, 1GB, or 2GB. Because it's a static parameter, it will require a server restart. If you have changed the parameter innodb_log_file_size from default, check if the value of "show global status like 'innodb_buffer_pool_pages_dirty'" stays at 0 for 30 seconds to avoid restart delay. See [Server parameters in Azure Database for MySQL](./concepts-server-parameters.md) to learn more. 
 
 - **Known Issues**
     - When a primary Azure region is down, one cannot create geo-redundant servers in it's geo-paired region as storage cannot be provisioned in the primary Azure region. One must wait for the primary region to be up to provision geo-redundant servers in the geo-paired region.