Made fixes suggested by PR reviewer and by Acrolinx.

Author: douglaslMS

docs/integration-services/ssis-quickstart-deploy-cmdline.md

@@ -19,7 +19,7 @@ For more info about the Integration Services Deployment Wizard, see [Integration
 
 2. Run `ISDeploymentWizard.exe`. The Integration Services Deployment Wizard opens.
 
-    If the folder that contains `ISDeploymentWizard.exe` is not in your `path` environment variable, you may have to use the `cd` command to change to its directory. For SQL Server 2017, this is typically `C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn`.
+    If the folder that contains `ISDeploymentWizard.exe` is not in your `path` environment variable, you may have to use the `cd` command to change to its directory. For SQL Server 2017, this folder is typically `C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn`.
 
 ## Deploy a project with the wizard
 1. On the **Introduction** page of the wizard, review the introduction. Click **Next** to open the **Select Source** page.
@@ -30,7 +30,7 @@ For more info about the Integration Services Deployment Wizard, see [Integration
     Click **Next** to see the **Select Destination** page.
 
 3.  On the **Select Destination** page, select the destination for the project.
-    -   Enter the fully-qualified server name. If the target server is an Azure SQL Database server, the name is in this format: `<server_name>.database.windows.net`.
+    -   Enter the fully qualified server name. If the target server is an Azure SQL Database server, the name is in this format: `<server_name>.database.windows.net`.
     -   Then click **Browse** to select the target folder in SSISDB.
     Click **Next** to open the **Review** page.  
 

docs/integration-services/ssis-quickstart-deploy-dotnet.md

@@ -21,13 +21,13 @@ Before you start, make sure you have Visual Studio or Visual Studio Code install
 > [!NOTE]
 > An Azure SQL Database server listens on port 1433. If you're trying to connect to an Azure SQL Database server from within a corporate firewall, this port must be open in the corporate firewall for you to connect successfully.
 
-## For SQL Database, get the connection info
+## Get the connection info, if deployed to SQL Database, 
 
 If your packages are deployed to an Azure SQL Database, get the connection information you need to connect to the SSIS Catalog database (SSISDB). You need the fully qualified server name and login information in the procedures that follow.
 
 1. Log in to the [Azure portal](https://portal.azure.com/).
 2. Select **SQL Databases** from the left-hand menu, and click the SSISDB database on the **SQL databases** page. 
-3. On the **Overview** page for your database, review the fully qualified server name. To bring up the **Click to copy** option, hover over the server name . 
+3. On the **Overview** page for your database, review the fully qualified server name. To bring up the **Click to copy** option, hover over the server name. 
 4. If you forget your Azure SQL Database server login information, navigate to the SQL Database server page to view the server admin name. You can reset the password if necessary.
 5. Click **Show database connection strings**.
 6. Review the complete **ADO.NET** connection string. The sample code uses a `SqlConnectionStringBuilder` to recreate this connection string with the individual parameter values that you provide.
@@ -46,9 +46,9 @@ If your packages are deployed to an Azure SQL Database, get the connection infor
     -   Microsoft.SqlServer.Management.Sdk.Sfc
     -   Microsoft.SqlServer.Smo
 4. Click the **Browse** button to add a reference to **Microsoft.SqlServer.Management.IntegrationServices**. (This assembly is installed only in the global assembly cache (GAC).) The **Select the files to reference** dialog box opens.
-5. In the **Select the files to reference** dialog box, navigate to the GAC folder that contains the assembly. Typically this is `C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\14.0.0.0__89845dcd8080cc91`.
+5. In the **Select the files to reference** dialog box, navigate to the GAC folder that contains the assembly. Typically this folder is `C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\14.0.0.0__89845dcd8080cc91`.
 6. Select the assembly (that is, the .dll file) in the folder and click **Add**.
-7. Click **OK** to close the **Reference Manager** dialog box and add the three references. Check the **References** list in Solution Explorer to make sure the references are there.
+7. Click **OK** to close the **Reference Manager** dialog box and add the three references. To make sure the references are there, check the **References** list in Solution Explorer.
 
 ## Add the C# code 
 1. Open **Program.cs**.
@@ -105,7 +105,7 @@ namespace deploy_ssis_project
 
 ## Run the code
 
-1. Press **F5** to run the application.
+1. To run the application, press **F5**.
 2. In SSMS, verify that the project has been deployed.
 
 ## Next steps

docs/integration-services/ssis-quickstart-deploy-ssms.md

@@ -57,7 +57,7 @@ Use SQL Server Management Studio to establish a connection to the SSIS Catalog.
     Click **Next** to see the **Select Destination** page.
 
 3.  On the **Select Destination** page, select the destination for the project.
-    -   Enter the fully-qualified server name. If the target server is an Azure SQL Database server, the name is in this format: `<server_name>.database.windows.net`.
+    -   Enter the fully qualified server name. If the target server is an Azure SQL Database server, the name is in this format: `<server_name>.database.windows.net`.
     -   Then click **Browse** to select the target folder in SSISDB.
     Click **Next** to open the **Review** page.  
 

docs/integration-services/ssis-quickstart-deploy-tsql-ssms.md

@@ -56,7 +56,7 @@ Run the following Transact-SQL code to deploy an SSIS project.
 
 4.  Run the script.
 
-5. In Object Explorer, refresh the contents of **SSISDB** if necessary and check for the project that you just deployed.
+5. In Object Explorer, refresh the contents of **SSISDB** if necessary and check for the project that you deployed.
 
 ```sql
 DECLARE @ProjectBinary AS varbinary(max)

docs/integration-services/ssis-quickstart-deploy-tsql-vscode.md

@@ -25,7 +25,7 @@ Before you start, make sure you have installed the latest version of Visual Stud
 
 ## Set language mode to SQL in VS Code
 
-Set the language mode is set to **SQL** in Visual Studio Code to enable mssql commands and T-SQL IntelliSense.
+To enable `mssql` commands and T-SQL IntelliSense, set the language mode is set to **SQL** in Visual Studio Code.
 
 1. Open Visual Studio Code and then open a new window. 
 
@@ -38,13 +38,13 @@ Set the language mode is set to **SQL** in Visual Studio Code to enable mssql co
 Use Visual Studio Code to establish a connection to the SSIS Catalog.
 
 > [!IMPORTANT]
-> Before continuing, make sure that you have your server, database, and login information ready. Once you begin entering the connection profile information, if you change your focus from Visual Studio Code, you have to restart creating the connection profile.
+> Before continuing, make sure that you have your server, database, and login information ready. If you change your focus from Visual Studio Code after you begin entering the connection profile information, you have to restart creating the connection profile.
 
 1. In VS Code, press **CTRL+SHIFT+P** (or **F1**) to open the Command Palette.
 
 2. Type **sqlcon** and press **ENTER**.
 
-3. Press **ENTER** to select **Create Connection Profile**. This creates a connection profile for your SQL Server instance.
+3. Press **ENTER** to select **Create Connection Profile**. This step creates a connection profile for your SQL Server instance.
 
 4. Follow the prompts to specify the connection properties for the new connection profile. After specifying each value, press **ENTER** to continue. 
 
@@ -55,7 +55,7 @@ Use Visual Studio Code to establish a connection to the SSIS Catalog.
    | **Authentication** | SQL Login| This quickstart uses SQL authentication. |
    | **User name** | The server admin account | This is the account that you specified when you created the server. |
    | **Password (SQL Login)** | The password for your server admin account | This is the password that you specified when you created the server. |
-   | **Save Password?** | Yes or No | Select Yes if you do not want to enter the password each time. |
+   | **Save Password?** | Yes or No | If you do not want to enter the password each time, select Yes. |
    | **Enter a name for this profile** | A profile name, such as **mySSISServer** | A saved profile name speeds your connection on subsequent logins. | 
 
 5. Press the **ESC** key to close the info message that informs you that the profile is created and connected.

docs/integration-services/ssis-quickstart-run-cmdline.md

@@ -17,15 +17,15 @@ This quick start tutorial demonstrates how to run an SSIS package from the comma
 
 For more info about `DTExec.exe`, see [dtexec Utility](https://docs.microsoft.com/en-us/sql/integration-services/packages/dtexec-utility).
 
-## Steps
+## Run a package with dtexec
 
-If the folder that contains `DTExec.exe` is not in your `path` environment variable, you may have to use the `cd` command to change to its directory. For SQL Server 2017, this is typically `C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn`.
+If the folder that contains `DTExec.exe` is not in your `path` environment variable, you may have to use the `cd` command to change to its directory. For SQL Server 2017, this folder is typically `C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn`.
 
 With the parameter values used in the following example, the program runs the package in the specified folder path on the SSIS server - that is, the server that hosts the SSIS Catalog database (SSISDB). The `/Server` parameter provides the server name. The program connects as the current user with Windows Integrated Authentication. To use SQL Authentication, specify the `/User` and `Password` parameters with appropriate values.
 
 1. Open a Command Prompt window.
 
-2. Run `DTExec.exe` and provide values at least for the `ISServer` and the `Server` parameters, as shown in the following example.
+2. Run `DTExec.exe` and provide values at least for the `ISServer` and the `Server` parameters, as shown in the following example:
 
     ```cmd
     dtexec /ISServer "\SSISDB\Project1Folder\Integration Services Project1\Package.dtsx" /Server "localhost"

docs/integration-services/ssis-quickstart-run-dotnet.md

@@ -1,5 +1,5 @@
 ---
-title: " | Microsoft Docs"
+title: "Run an SSIS project with .NET code (C#) | Microsoft Docs"
 ms.date: "09/25/2017"
 ms.topic: "article"
 ms.prod: "sql-server-2017"
@@ -21,13 +21,13 @@ Before you start, make sure you have Visual Studio or Visual Studio Code install
 > [!NOTE]
 > An Azure SQL Database server listens on port 1433. If you're trying to connect to an Azure SQL Database server from within a corporate firewall, this port must be open in the corporate firewall for you to connect successfully.
 
-## For SQL Database, get the connection info
+## Get the connection info, if deployed to SQL Database, 
 
 If your packages are deployed to an Azure SQL Database, get the connection information you need to connect to the SSIS Catalog database (SSISDB). You need the fully qualified server name and login information in the procedures that follow.
 
 1. Log in to the [Azure portal](https://portal.azure.com/).
 2. Select **SQL Databases** from the left-hand menu, and click the SSISDB database on the **SQL databases** page. 
-3. On the **Overview** page for your database, review the fully qualified server name. To bring up the **Click to copy** option, hover over the server name . 
+3. On the **Overview** page for your database, review the fully qualified server name. To bring up the **Click to copy** option, hover over the server name. 
 4. If you forget your Azure SQL Database server login information, navigate to the SQL Database server page to view the server admin name. You can reset the password if necessary.
 5. Click **Show database connection strings**.
 6. Review the complete **ADO.NET** connection string. The sample code uses a `SqlConnectionStringBuilder` to recreate this connection string with the individual parameter values that you provide.
@@ -46,9 +46,9 @@ If your packages are deployed to an Azure SQL Database, get the connection infor
     -   Microsoft.SqlServer.Management.Sdk.Sfc
     -   Microsoft.SqlServer.Smo
 4. Click the **Browse** button to add a reference to **Microsoft.SqlServer.Management.IntegrationServices**. (This assembly is installed only in the global assembly cache (GAC).) The **Select the files to reference** dialog box opens.
-5. In the **Select the files to reference** dialog box, navigate to the GAC folder that contains the assembly. Typically this is `C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\14.0.0.0__89845dcd8080cc91`.
+5. In the **Select the files to reference** dialog box, navigate to the GAC folder that contains the assembly. Typically this folder is `C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\14.0.0.0__89845dcd8080cc91`.
 6. Select the assembly (that is, the .dll file) in the folder and click **Add**.
-7. Click **OK** to close the **Reference Manager** dialog box and add the three references. Check the **References** list in Solution Explorer to make sure the references are there.
+7. Click **OK** to close the **Reference Manager** dialog box and add the three references. To make sure the references are there, check the **References** list in Solution Explorer.
 
 ## Add the C# code 
 1. Open **Program.cs**.
@@ -105,7 +105,7 @@ namespace run_ssis_package
 
 ## Run the code
 
-1. Press **F5** to run the application.
+1. To run the application, press **F5**.
 2. Verify that the package ran as expected and then close the application window.
 
 ## Next steps

docs/integration-services/ssis-quickstart-run-tsql-ssms.md

@@ -44,15 +44,15 @@ Use SQL Server Management Studio to establish a connection to the SSIS Catalog o
 ## Run a package
 Run the following Transact-SQL code to run an SSIS package.
 
-1.  In SSMS, open a new query window and paste the following code. (This is the code generated by the **Script** option in the **Execute Package** dialog box in SSMS.)
+1.  In SSMS, open a new query window and paste the following code. (This code is the code generated by the **Script** option in the **Execute Package** dialog box in SSMS.)
 
 2.  Update the parameter values in the `catalog.create_execution` stored procedure for your system.
 
 3.  Make sure that SSISDB is the current database.
 
 4.  Run the script.
 
-5. In Object Explorer, refresh the contents of **SSISDB** if necessary and check for the project that you just deployed.
+5. In Object Explorer, refresh the contents of **SSISDB** if necessary and check for the project that you deployed.
 
 ```sql
 Declare @execution_id bigint

docs/integration-services/ssis-quickstart-run-tsql-vscode.md

@@ -22,7 +22,7 @@ Before you start, make sure you have installed the latest version of Visual Stud
 
 ## Set language mode to SQL in VS Code
 
-Set the language mode is set to **SQL** in Visual Studio Code to enable mssql commands and T-SQL IntelliSense.
+To enable `mssql` commands and T-SQL IntelliSense, set the language mode is set to **SQL** in Visual Studio Code.
 
 1. Open Visual Studio Code and then open a new window. 
 
@@ -35,13 +35,13 @@ Set the language mode is set to **SQL** in Visual Studio Code to enable mssql co
 Use Visual Studio Code to establish a connection to the SSIS Catalog.
 
 > [!IMPORTANT]
-> Before continuing, make sure that you have your server, database, and login information ready. Once you begin entering the connection profile information, if you change your focus from Visual Studio Code, you have to restart creating the connection profile.
+> Before continuing, make sure that you have your server, database, and login information ready. If you change your focus from Visual Studio Code after you begin entering the connection profile information, you have to restart creating the connection profile.
 
 1. In VS Code, press **CTRL+SHIFT+P** (or **F1**) to open the Command Palette.
 
 2. Type **sqlcon** and press **ENTER**.
 
-3. Press **ENTER** to select **Create Connection Profile**. This creates a connection profile for your SQL Server instance.
+3. Press **ENTER** to select **Create Connection Profile**. This step creates a connection profile for your SQL Server instance.
 
 4. Follow the prompts to specify the connection properties for the new connection profile. After specifying each value, press **ENTER** to continue. 
 
@@ -52,7 +52,7 @@ Use Visual Studio Code to establish a connection to the SSIS Catalog.
    | **Authentication** | SQL Login| This quickstart uses SQL authentication. |
    | **User name** | The server admin account | This is the account that you specified when you created the server. |
    | **Password (SQL Login)** | The password for your server admin account | This is the password that you specified when you created the server. |
-   | **Save Password?** | Yes or No | Select Yes if you do not want to enter the password each time. |
+   | **Save Password?** | Yes or No | If you do not want to enter the password each time, select Yes. |
    | **Enter a name for this profile** | A profile name, such as **mySSISServer** | A saved profile name speeds your connection on subsequent logins. | 
 
 5. Press the **ESC** key to close the info message that informs you that the profile is created and connected.
@@ -62,7 +62,7 @@ Use Visual Studio Code to establish a connection to the SSIS Catalog.
 ## Run the T-SQL code
 Run the following Transact-SQL code to run an SSIS package.
 
-1. In the **Editor** window, enter the following query in the empty query window. (This is the code generated by the **Script** option in the **Execute Package** dialog box in SSMS.)
+1. In the **Editor** window, enter the following query in the empty query window. (This code is the code generated by the **Script** option in the **Execute Package** dialog box in SSMS.)
 
 2. Update the parameter values in the `catalog.create_execution` stored procedure for your system.