acrolinx fixes

markingmyname · markingmyname · commit 315bff806834 · 2023-04-19T10:45:59.000-05:00
diff --git a/articles/mysql/flexible-server/connect-nodejs.md b/articles/mysql/flexible-server/connect-nodejs.md
@@ -107,15 +107,15 @@ Get the connection information needed to connect to the Azure Database for MySQL
 
 1. Paste the JavaScript code into new text files, and then save it into a project folder with file extension .js (such as C:\nodejsmysql\createtable.js or /home/username/nodejsmysql/createtable.js).
 1. Replace `host`, `user`, `password` and `database` config options in the code with the values that you specified when you created the MySQL flexible server and database.
-1. **Obtain SSL certificate**: To use encrypted connections with your client applications,you will need to download the [public SSL certificate](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem) which is also available in Azure portal Networking blade as shown in the screenshot below.
+1. **Obtain SSL certificate**: To use encrypted connections with your client applications,you'll need to download the [public SSL certificate](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem) which is also available in Azure portal Networking blade as shown in the screenshot below.
     :::image type="content" source="./media/how-to-connect-tls-ssl/download-ssl.png" alt-text="Screenshot showing how to download public SSL certificate from Azure portal." lightbox="./media/how-to-connect-tls-ssl/download-ssl.png":::
 
 Save the certificate file to your preferred location.
 
 1. In the `ssl` config option, replace the `ca-cert` filename with the path to this local file. This will allow the application to connect securely to the database over SSL.
 1. Open the command prompt or bash shell, and then change directory into your project folder `cd nodejsmysql`.
 1. To run the application, enter the node command followed by the file name, such as `node createtable.js`.
-1. On Windows, if the node application is not in your environment variable path, you may need to use the full path to launch the node application, such as `"C:\Program Files\nodejs\node.exe" createtable.js`
+1. On Windows, if the node application isn't in your environment variable path, you may need to use the full path to launch the node application, such as `"C:\Program Files\nodejs\node.exe" createtable.js`
 
 ## Connect, create table, and insert data
 
diff --git a/articles/mysql/single-server/concepts-migrate-dump-restore.md b/articles/mysql/single-server/concepts-migrate-dump-restore.md
@@ -19,7 +19,7 @@ This article explains two common ways to back up and restore databases in your A
 - Dump and restore from the command-line (using mysqldump)
 - Dump and restore using PHPMyAdmin
 
-You can also refer to [Database Migration Guide](https://github.com/Azure/azure-mysql/tree/master/MigrationGuide) for detailed information and use cases about migrating databases to Azure Database for MySQL. This guide provides guidance that will lead the successful planning and execution of a MySQL migration to Azure.
+You can also refer to [Database Migration Guide](https://github.com/Azure/azure-mysql/tree/master/MigrationGuide) for detailed information and use cases about migrating databases to Azure Database for MySQL. This guide provides guidance that leads the successful planning and execution of a MySQL migration to Azure.
 
 ## Before you begin
 To step through this how-to guide, you need to have:
@@ -75,8 +75,8 @@ Add the connection information into your MySQL Workbench.
 ## Preparing the target Azure Database for MySQL server for fast data loads
 To prepare the target Azure Database for MySQL server for faster data loads, the following server parameters and configuration needs to be changed.
 - max_allowed_packet – set to 1073741824 (that is, 1 GB) to prevent any overflow issue due to long rows.
-- slow_query_log – set to OFF to turn off the slow query log. This will eliminate the overhead caused by slow query logging during data loads.
-- query_store_capture_mode – set to NONE to turn off the Query Store. This will eliminate the overhead caused by sampling activities by Query Store.
+- slow_query_log – set to OFF to turn off the slow query log. This eliminates the overhead caused by slow query logging during data loads.
+- query_store_capture_mode – set to NONE to turn off the Query Store. This eliminates the overhead caused by sampling activities by Query Store.
 - innodb_buffer_pool_size – Scale up the server to 32 vCore Memory Optimized SKU from the Pricing tier of the portal during migration to increase the innodb_buffer_pool_size. Innodb_buffer_pool_size can only be increased by scaling up compute for Azure Database for MySQL server.
 - innodb_io_capacity & innodb_io_capacity_max - Change to 9000 from the Server parameters in Azure portal to improve the IO utilization to optimize for migration speed.
 - innodb_write_io_threads & innodb_write_io_threads - Change to 4 from the Server parameters in Azure portal to improve the speed of migration.
@@ -170,4 +170,4 @@ For known issues, tips and tricks, we recommend you to look at our [techcommunit
 ## Next steps
 - [Connect applications to Azure Database for MySQL](./how-to-connection-string.md).
 - For more information about migrating databases to Azure Database for MySQL, see the [Database Migration Guide](https://github.com/Azure/azure-mysql/tree/master/MigrationGuide).
-- If you're looking to migrate large databases with database sizes more than 1 TBs, you may want to consider using community tools like **mydumper/myloader** which supports parallel export and import. Learn [how to migrate large MySQL databases](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/best-practices-for-migrating-large-databases-to-azure-database/ba-p/1362699).
+- If you're looking to migrate large databases with database sizes more than 1 TB, you may want to consider using community tools like **mydumper/myloader** which supports parallel export and import. Learn [how to migrate large MySQL databases](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/best-practices-for-migrating-large-databases-to-azure-database/ba-p/1362699).
diff --git a/articles/mysql/single-server/concepts-ssl-connection-security.md b/articles/mysql/single-server/concepts-ssl-connection-security.md
@@ -34,7 +34,7 @@ When provisioning a new Azure Database for MySQL server through the Azure portal
 
 Connection strings for various programming languages are shown in the Azure portal. Those connection strings include the required SSL parameters to connect to your database. In the Azure portal, select your server. Under the **Settings** heading, select the **Connection strings**. The SSL parameter varies based on the connector, for example "ssl=true" or "sslmode=require" or "sslmode=required" and other variations.
 
-In some cases, applications require a local certificate file generated from a trusted Certificate Authority (CA) certificate file to connect securely. Currently customers can **only use** the predefined certificate to connect to an Azure Database for MySQL server which is located at https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem. 
+In some cases, applications require a local certificate file generated from a trusted Certificate Authority (CA) certificate file to connect securely. Currently customers can **only use** the predefined certificate to connect to an Azure Database for MySQL server, which is located at https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem. 
 
 Similarly, the following links point to the certificates for servers in sovereign clouds: [Azure Government](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem), [Azure China](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem), and [Azure Germany](https://www.d-trust.net/cgi-bin/D-TRUST_Root_Class_3_CA_2_2009.crt).
 
@@ -56,18 +56,18 @@ Azure Database for MySQL provides the ability to enforce the TLS version for the
 | TLS1_2                           | TLS version 1.2  and higher                     |
 
 
-For example, setting the value of minimum TLS setting version to TLS 1.0 means your server will allow connections from clients using TLS 1.0, 1.1, and 1.2+. Alternatively, setting this to 1.2 means that you only allow connections from clients using TLS 1.2+ and all connections with TLS 1.0 and TLS 1.1 will be rejected.
+For example, setting the value of minimum TLS setting version to TLS 1.0 means your server allows connections from clients using TLS 1.0, 1.1, and 1.2+. Alternatively, setting this to 1.2 means that you only allow connections from clients using TLS 1.2+ and all connections with TLS 1.0 and TLS 1.1 will be rejected.
 
 > [!NOTE] 
 > By default, Azure Database for MySQL does not enforce a minimum TLS version (the setting `TLSEnforcementDisabled`).
 >
 > Once you enforce a minimum TLS version, you cannot later disable minimum version enforcement.
 
-The minimum TLS version setting doesnt require any restart of the server can be set while the server is online. To learn how to set the TLS setting for your Azure Database for MySQL, refer to [How to configure TLS setting](how-to-tls-configurations.md).
+The minimum TLS version setting doesn't require any restart of the server can be set while the server is online. To learn how to set the TLS setting for your Azure Database for MySQL, refer to [How to configure TLS setting](how-to-tls-configurations.md).
 
 ## Cipher support by Azure Database for MySQL single server
 
-As part of the SSL/TLS communication, the cipher suites are validated and only support cipher suits are allowed to communicate to the database serer. The cipher suite validation is controlled in the [gateway layer](concepts-connectivity-architecture.md#connectivity-architecture) and not explicitly on the node itself. If the cipher suites doesn't match one of suites listed below, incoming client connections will be rejected.
+As part of the SSL/TLS communication, the cipher suites are validated and only support cipher suits are allowed to communicate to the database server. The cipher suite validation is controlled in the [gateway layer](concepts-connectivity-architecture.md#connectivity-architecture) and not explicitly on the node itself. If the cipher suites don't match one of suites listed below, incoming client connections will be rejected.
 
 ### Cipher suite supported
 
diff --git a/articles/mysql/single-server/connect-nodejs.md b/articles/mysql/single-server/connect-nodejs.md
@@ -19,7 +19,7 @@ ms.date: 06/20/2022
 
 In this quickstart, you connect to an Azure Database for MySQL by using Node.js. You then use SQL statements to query, insert, update, and delete data in the database from Mac, Ubuntu Linux, and Windows platforms. 
 
-This topic assumes that you're familiar with developing using Node.js, but you're new to working with Azure Database for MySQL.
+This article assumes that you're familiar with developing using Node.js, but you're new to working with Azure Database for MySQL.
 
 ## Prerequisites
 
@@ -109,7 +109,7 @@ Get the connection information needed to connect to the Azure Database for MySQL
 1. In the `ssl` config option, replace the `ca-cert` filename with the path to this local file.
 1. Open the command prompt or bash shell, and then change directory into your project folder `cd nodejsmysql`.
 1. To run the application, enter the node command followed by the file name, such as `node createtable.js`.
-1. On Windows, if the node application is not in your environment variable path, you may need to use the full path to launch the node application, such as `"C:\Program Files\nodejs\node.exe" createtable.js`
+1. On Windows, if the node application isn't in your environment variable path, you may need to use the full path to launch the node application, such as `"C:\Program Files\nodejs\node.exe" createtable.js`
 
 ## Connect, create table, and insert data
 
diff --git a/articles/mysql/single-server/connect-workbench.md b/articles/mysql/single-server/connect-workbench.md
@@ -12,6 +12,7 @@ ms.custom:
   - mvc
   - mode-other
 ---
+
 # Quickstart: Use MySQL Workbench to connect and query data in Azure Database for MySQL
 
 [!INCLUDE[applies-to-mysql-single-server](../includes/applies-to-mysql-single-server.md)]
@@ -23,6 +24,7 @@ This quickstart demonstrates how to connect to an Azure Database for MySQL using
 ## Prerequisites
 
 This quickstart uses the resources created in either of these guides as a starting point:
+
 - [Create an Azure Database for MySQL server using Azure portal](./quickstart-create-mysql-server-database-using-azure-portal.md)
 - [Create an Azure Database for MySQL server using Azure CLI](./quickstart-create-mysql-server-database-using-azure-cli.md)
 
@@ -54,17 +56,17 @@ To connect to Azure MySQL Server by using the GUI tool MySQL Workbench:
 
 1. In **Setup New Connection** dialog box, enter the following information on the **Parameters** tab:
 
-:::image type="content" source="./media/connect-workbench/2-setup-new-connection.png" alt-text="setup new connection" lightbox="./media/connect-workbench/2-setup-new-connection.png":::
-
-| **Setting** | **Suggested value** | **Field description** |
-| --- | --- | --- |
-| Connection Name | Demo Connection | Specify a label for this connection. |
-| Connection Method | Standard (TCP/IP) | Standard (TCP/IP) is sufficient. |
-| Hostname | *server name* | Specify the server name value that was used when you created the Azure Database for MySQL earlier. Our example server shown is mydemoserver.mysql.database.azure.com. Use the fully qualified domain name (\*.mysql.database.azure.com) as shown in the example. Follow the steps in the previous section to get the connection information if you do not remember your server name. |
-| Port | 3306 | Always use port 3306 when connecting to Azure Database for MySQL. |
-| Username |  *server admin login name* | Type in the server admin login username supplied when you created the Azure Database for MySQL earlier. Our example username is myadmin@mydemoserver. Follow the steps in the previous section to get the connection information if you do not remember the username. The format is *username\@servername*.
-| Password | your password | Select **Store in Vault...** button to save the password. |
+    :::image type="content" source="./media/connect-workbench/2-setup-new-connection.png" alt-text="setup new connection" lightbox="./media/connect-workbench/2-setup-new-connection.png":::
 
+    | **Setting** | **Suggested value** | **Field description** |
+    | --- | --- | --- |
+    | Connection Name | Demo Connection | Specify a label for this connection. |
+    | Connection Method | Standard (TCP/IP) | Standard (TCP/IP) is sufficient. |
+    | Hostname | *server name* | Specify the server name value that was used when you created the Azure Database for MySQL earlier. Our example server shown is mydemoserver.mysql.database.azure.com. Use the fully qualified domain name (\*.mysql.database.azure.com) as shown in the example. Follow the steps in the previous section to get the connection information if you don't remember your server name. |
+    | Port | 3306 | Always use port 3306 when connecting to Azure Database for MySQL. |
+    | Username |  *server admin login name* | Type in the server admin login username supplied when you created the Azure Database for MySQL earlier. Our example username is myadmin@mydemoserver. Follow the steps in the previous section to get the connection information if you don't remember the username. The format is *username\@servername*.
+    | Password | your password | Select **Store in Vault...** button to save the password. |
+    
 1. Select **Test Connection** to test if all parameters are correctly configured.
 
 1. Select **OK** to save the connection.
@@ -112,7 +114,9 @@ To connect to Azure MySQL Server by using the GUI tool MySQL Workbench:
     :::image type="content" source="media/connect-workbench/3-workbench-sql-tab.png" alt-text="MySQL Workbench SQL Tab to run sample SQL code" lightbox="media/connect-workbench/3-workbench-sql-tab.png":::
 
 1. To run the sample SQL Code, select the lightening bolt icon in the toolbar of the **SQL File** tab.
+
 1. Notice the three tabbed results in the **Result Grid** section in the middle of the page.
+
 1. Notice the **Output** list at the bottom of the page. The status of each command is shown.
 
 Now, you have connected to Azure Database for MySQL by using MySQL Workbench, and you have queried data using the SQL language.
