Addressed all blocking issues

Author: markingmyname

docs/azure-data-studio/quickstart-mysql.md

@@ -12,7 +12,7 @@ ms.custom: intro-quickstart, ignite-2022
 
 # Quickstart: Use Azure Data Studio to connect and query MySQL (Preview)
 
-This quickstart shows how to use Azure Data Studio to connect to a MySQL server (hosted on-premises, on VMs, on managed MySQL in other clouds or on Azure Database for MySQL - FLexible Server), create a database, and use SQL statements to insert and query data in the database.
+This quickstart shows how to use Azure Data Studio to connect to a MySQL server (hosted on-premises, on VMs, on managed MySQL in other clouds or on Azure Database for MySQL - Flexible Server), create a database, and use SQL statements to insert and query data in the database.
 
 ## Prerequisites
 
@@ -29,7 +29,7 @@ To complete this quickstart, you need Azure Data Studio, the MySQL extension for
 
 1. Start **Azure Data Studio**.
 
-2. The first time you start Azure Data Studio the **Connection** dialog opens. If the **Connection** dialog doesn't open, click the **New Connection** icon on the **SERVERS** view in the **Connections** tab:
+2. The first time you start Azure Data Studio the **Connection** dialog opens. If the **Connection** dialog doesn't open, select the **New Connection** icon on the **SERVERS** view in the **Connections** tab:
 
     :::image type="content" source="media/quickstart-mysql/new-connection-icon.png" alt-text="Screenshot of new connection icon in the Servers sidebar.":::
 
@@ -42,14 +42,14 @@ To complete this quickstart, you need Azure Data Studio, the MySQL extension for
    | Setting       | Example value | Description |
    | ------------ | ------------------ | ------------------------------------------------- |
    | **Server name** | localhost / exampleserver.mysql.database.azure.con | The fully qualified server name. |
-   | **User name** | mysqluser | The user name you want to log in with. |
-   | **Password (SQL Login)** | *password* | The password for the user account you are logging in with. |
+   | **User name** | mysqluser | The user name you want to sign in with. |
+   | **Password (SQL Login)** | *password* | The password for the user account you're logging in with. |
    | **Remember Password** | *Check* | Check this box if you don't want to enter the password each time you connect. |
    | **Database name** | \<Default\> | Enter a database name if you want the connection to specify a database. |
    | **Server group** | \<Default\> | This option lets you assign this connection to a specific server group you create. |
    | **Name (optional)** | *leave blank* | This option lets you specify a friendly name for your server. |
 
-5. If your MySQL server requires SSL encryptions, navigate to **Advanced Properties** window by selecting **Advanced...** button, enter the SSL configuration details and select **OK**. By default, SSL mode is configured as *Require*. For more details on SSL encryption and modes, see [Configuring MySQL to Use Encrypted Connections](https://dev.mysql.com/doc/refman/8.0/en/using-encrypted-connections.html).
+5. If your MySQL server requires SSL encryptions, navigate to **Advanced Properties** window by selecting **Advanced...** button, enter the SSL configuration details and select **OK**. By default, SSL mode is configured as *Require*. For more information on SSL encryption and modes, see [Configuring MySQL to Use Encrypted Connections](https://dev.mysql.com/doc/refman/8.0/en/using-encrypted-connections.html).
 
 6. Review the connection details and select **Connect**.
 
@@ -67,7 +67,7 @@ The following steps will create a database named **tutorialdb**:
    CREATE DATABASE tutorialdb;
    ```
 
-3. From the toolbar select **Run** to execute the query. Notifications appear in the **MESSAGES** pane to show query progress.
+3. From the toolbar, select **Run** to execute the query. Notifications appear in the **MESSAGES** pane to show query progress.
 
 >[!TIP]
 > You can use **F5** on your keyboard to execute the statement instead of using **Run**.
@@ -101,7 +101,7 @@ After the query completes, right-click **Databases** under your MySQL server in
 
 ## Insert data
 
-Paste the following snippet into the query window and click **Run**:
+Paste the following snippet into the query window and select **Run**:
 
    ```sql
    -- Insert rows into table 'customers'

…owepivot-upgrade-flow-sharepoint2010.png …r-pivot-upgrade-flow-sharepoint-2010.pngdocs/database-engine/install-windows/media/upgrade-power-pivot-for-sharepoint/as-powepivot-upgrade-flow-sharepoint2010.png renamed to docs/database-engine/install-windows/media/upgrade-power-pivot-for-sharepoint/as-power-pivot-upgrade-flow-sharepoint-2010.png docs/database-engine/install-windows/media/upgrade-power-pivot-for-sharepoint/as-powepivot-upgrade-flow-sharepoint2010.png renamed to docs/database-engine/install-windows/media/upgrade-power-pivot-for-sharepoint/as-power-pivot-upgrade-flow-sharepoint-2010.png

@@ -10,98 +10,102 @@ ms.technology: integration-services
 ms.topic: conceptual
 ---
 
-# Microsoft connector for Teradata (SSIS)
+# Microsoft Connector for Teradata (SSIS)
 
 [!INCLUDE[sqlserver-ssis](../../includes/applies-to-version/sqlserver-ssis.md)]
 
-Microsoft connector for Teradata enables exporting data from and load data into Teradata databases in an SSIS package.
+Microsoft Connector for Teradata enables exporting and loading data into Teradata databases in an SSIS package.
 
 This new connector supports databases with 1MB-enabled tables.
 
 ## Version support
 
-The following Microsoft SQL Server products are supported by Microsoft Connector for Teradata:
+Microsoft Connector supports the following Microsoft SQL Server products for Teradata:
 
 - Microsoft SQL Server 2019
 - Microsoft SQL Server Data Tools (SSDT) 15.8.1 or later for Visual Studio 2017
 - Microsoft SQL Server Data Tools (SSDT) for Visual Studio 2019
 
-Microsoft connector for Teradata uses ODBC Driver for Teradata and Teradata Parallel Transporter shipped with Teradata Tools and Utilities (TTU). Supported TTU versions are 16.20 and 17.10.
+Microsoft Connector for Teradata uses ODBC Driver for Teradata, and Teradata Parallel Transporter shipped with Teradata Tools and Utilities (TTU). Supported TTU versions are 16.20 and 17.10.
 
 ## Installation
 
 Install TTU from [Teradata site](https://downloads.teradata.com/download/database/teradata-tools-and-utilities-13-10). Make sure that ODBC Driver for Teradata and Teradata Parallel Transporter features is selected during the installation.
 
-To install the connector for Teradata database, download and run the installer from [the latest version of Microsoft connector for Teradata](https://www.microsoft.com/download/details.aspx?id=100599). Then follow the directions in the installation wizard.
+To install the connector for the Teradata database, download and run the installer from [the latest version of Microsoft connector for Teradata](https://www.microsoft.com/download/details.aspx?id=100599). Then follow the directions in the installation wizard.
 
-After you install the connector, you must restart the SQL Server Integration Service to be sure that the Teradata source and destination works correctly.
+After you install the connector, you must restart the SQL Server Integration Service to be sure that the Teradata source and destination work correctly.
 
 ## Design and execute SSIS packages
 
-Microsoft Connector for Teradata provides similar user experience with Attunity Teradata Connector. User can design new packages based on previous experience, using SSDT for VS 2017 or VS 2019, with *targeting SQL server 2019*.
+Microsoft Connector for Teradata provides a similar user experience to Attunity Teradata Connector. Users can design new packages based on previous experience, using SSDT for VS 2017 or VS 2019, with *targeting SQL server 2019*.
 
 Teradata source and destination are under Common category.
 
 :::image type="content" source="media/teradata-connector/teradata-component.png" alt-text="Screenshot the Teradata Component.":::
 
-Teradata connection manager is displayed as "TERADATA".
+Teradata connection manager is displayed as "TERADATA."
 
 :::image type="content" source="media/teradata-connector/teradata-connection-manager-type.png" alt-text="Screenshot of the Teradata connection manager type":::
 
-Existing SSIS packages that have been designed with Attunity Teradata Connector will be automatically upgraded to use Microsoft Connector for Teradata. The icons will be changed as well.
+Existing SSIS packages designed with Attunity Teradata Connector will be automatically upgraded to use Microsoft Connector for Teradata. The icons will be changed as well.
 
-To execute SSIS package *targeting SQL Server 2017 and below*, you'll need to install **Microsoft Connector for Teradata by Attunity** with corresponding version from below link:
+To execute the SSIS package *targeting SQL Server 2017 and below*, you'll need to install **Microsoft Connector for Teradata by Attunity** with corresponding version from the below link:
 
 - [SQL Server 2017: Microsoft Connector Version 5.0 for Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=55179)
 - [SQL Server 2016: Microsoft Connector Version 4.0 for Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=52950)
 - [SQL Server 2014: Microsoft Connector Version 3.0 for Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=44582)
 - [SQL Server 2012: Microsoft Connector Version 2.0 for Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=29283)
 
-To design SSIS package in SSDT *targeting SQL Server 2017 and below*, you'll need to have **Microsoft Connector for Teradata** and install **Microsoft Connector for Teradata by Attunity** with corresponding version.
+To design the SSIS package in SSDT *targeting SQL Server 2017 and below*, you'll need to have **Microsoft Connector for Teradata** and install **Microsoft Connector for Teradata by Attunity** with the corresponding version.
 
-## Limitations and known issues
+## Limitations and known issues
 
-- Teradata Source/Destination Editor, **Default database** property doesn't take effective. As work-around, type database name in dropdown box to filter table or view.
+- Teradata Source/Destination Editor, **Default database** property doesn't take effect. As a workaround, type the database name in dropdown box to filter table or view.
 
-- Teradata Source/Destination Editor, Mapping step doesn't work when type `\<database>.<table/view>`. As work-around, type `\<database>.<table/view>`, then select the drop-down button.
+- Teradata Source/Destination Editor, Mapping step doesn't work when type `\<database>.<table/view>`. As work-around, type `\<database>.<table/view>`, then select the drop-down button.
 
-- Teradata Source Editor, view can't be displayed when Data access mode is "Table Name – TPT Export". As work-around, use Advanced Editor of Teradata Source.
+- Teradata Source Editor, view can't be displayed when Data access mode is "Table Name – TPT Export." As work-around, use Advanced Editor of Teradata Source.
 
-- Teradata Destination, attribute "PackMaximum" can't be set to "True". Otherwise, error will occur.
+- Teradata Destination, attribute "PackMaximum" can't be set to "True." Otherwise, error will occur.
 
 - Teradata Source always reads columns in the order as they're defined in the table. ODBC, on the other hand, requires columns be read in a specific order in certain circumstances [Getting Long Data](../../odbc/reference/develop-app/getting-long-data.md) and [SQLGetData](../../relational-databases/native-client-odbc-api/sqlgetdata.md). When the two orders don't match, read fails with error message "Invalid descriptor index, descriptor record doesn't exist, or descriptor record wasn't properly initialized."
 
-- Installing a new version over an old installation won't remove the old version entry from the installed program list. While this doesn't impact functioning of the new version, user can manually uninstall the old version in control panel "Programs, and Features" to get rid of the old version entry.
+- Installing a new version over an old installation won't remove the old version entry from the installed program list. While this doesn't impact functioning of the new version, user can manually uninstall the old version in the control panel "Programs, and Features" to get rid of the old version entry.
 
 ## Uninstallation
 
-You can run uninstall wizard to remove **Microsoft connector for Teradata**.
+You can uninstall wizard to remove **Microsoft connector for Teradata**.
 
 ## Release Notes
 
 ### Rev. 233
 
-**Bugfixes**
+**Bug fixes**
+
 - In a newly created Teradata Connection Manager, some required connection string properties like `DRIVER` aren't populated by default.
 
 ### Rev. 225
 
 **New Features**
+
 - Add support for TTU 17.10.
 
-**Bugfixes**
-- Incorrect data may be loaded by Teradata Source under certain circumstances.
-- Default error table in Teradata Destination is incorrectly named and may not be created in the database of destination table.
+**Bug fixes**
+
+- Teradata Source may load incorrect data under certain circumstances.
+- Default error table in Teradata Destination is incorrectly named and may not be created in the database of the destination table.
 - Options specified in the connection string property of Teradata Connection Manager may not be picked up and therefore don't take effect.
 
 ### Rev. 197
 
-**Bugfixes**
-- When reading empty string data, Teradata Source would fail with error message "An error occurred when converting string to target codepage."
+**Bug fixes**
+
+- When reading empty string data, Teradata Source would fail with the error message "An error occurred when converting string to target codepage."
 
 ## Next steps
 
 - Configure [Teradata connection manager](teradata-connection-manager.md)
 - Configure [Teradata source](teradata-source.md)
 - Configure [Teradata destination](teradata-destination.md)
-- If you have questions, visit [Tech Community](https://aka.ms/AA6iwdw).
+- If you have questions, visit [Tech Community](https://aka.ms/AA6iwdw)