Merge pull request #5645 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)

Author: ghogen

docs/debugger/walkthrough-writing-a-visualizer-in-csharp.md

@@ -59,7 +59,7 @@ Follow the tasks below to create a visualizer.
 
 5. Click **OK**.
 
-6. In DebuggerSide.cs, add the following statement to the `using` statements:
+6. In DebuggerSide.cs, add the following to the `using` directives:
 
    ```csharp
    using Microsoft.VisualStudio.DebuggerVisualizers;
@@ -93,7 +93,7 @@ Follow the tasks below to create a visualizer.
   }
   ```
 
-  The `Show` method contains the code that actually creates the visualizer dialog box or other user interface and displays the information that has been passed to the visualizer from the debugger. You must add the code that creates the dialog box and displays the information. In this walkthrough, you will do this using a Windows forms message box. First, you must add a reference and `using` statement for System.Windows.Forms.
+  The `Show` method contains the code that actually creates the visualizer dialog box or other user interface and displays the information that has been passed to the visualizer from the debugger. You must add the code that creates the dialog box and displays the information. In this walkthrough, you will do this using a Windows forms message box. First, you must add a reference and `using` directive for System.Windows.Forms.
 
 ### To add System.Windows.Forms
 
@@ -105,7 +105,7 @@ Follow the tasks below to create a visualizer.
 
 3. Click **OK**.
 
-4. In DebuggerSide.cs, add the following statement to the `using` statements:
+4. In DebuggerSide.cs, add the following to the `using` directives:
 
    ```csharp
    using System.Windows.Forms;
@@ -129,7 +129,7 @@ Follow the tasks below to create a visualizer.
 
 ### To add the debuggee-side code
 
-1. Add the following attribute code to DebuggerSide.cs, after the `using` statements but before `namespace MyFirstVisualizer`:
+1. Add the following attribute code to DebuggerSide.cs, after the `using` directives but before `namespace MyFirstVisualizer`:
 
    ```csharp
    [assembly:System.Diagnostics.DebuggerVisualizer(
@@ -199,7 +199,7 @@ Follow the tasks below to create a visualizer.
     > [!NOTE]
     > [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] automatically changes the class declaration in TestConsole.cs to match the new file name.
 
-3. In TestConsole.cs, add the following code to the `using` statements:
+3. In TestConsole.cs, add the following code to the `using` directives:
 
    ```csharp
    using MyFirstVisualizer;
@@ -264,4 +264,4 @@ First, you have to create a new class library project.
 
 - [Visualizer Architecture](../debugger/visualizer-architecture.md)
 - [How to: Install a Visualizer](../debugger/how-to-install-a-visualizer.md)
-- [Create Custom Visualizers](../debugger/create-custom-visualizers-of-data.md)
+- [Create Custom Visualizers](../debugger/create-custom-visualizers-of-data.md)

docs/deployment/how-to-retrieve-query-string-information-in-an-online-clickonce-application.md

@@ -40,7 +40,7 @@ The *query string* is the portion of a URL beginning with a question mark (?) th
 
 ### To obtain query string information from a ClickOnce application
 
-1. Place the following code in your project. In order for this code to function, you will have to have a reference to System.Web and add `using` or `Imports` statements for System.Web, System.Collections.Specialized, and System.Deployment.Application.
+1. Place the following code in your project. In order for this code to function, you will have to have a reference to System.Web and add `using` or `Imports` directives for System.Web, System.Collections.Specialized, and System.Deployment.Application.
 
      [!code-csharp[ClickOnceQueryString#1](../deployment/codesnippet/CSharp/how-to-retrieve-query-string-information-in-an-online-clickonce-application_1.cs)]
      [!code-vb[ClickOnceQueryString#1](../deployment/codesnippet/VisualBasic/how-to-retrieve-query-string-information-in-an-online-clickonce-application_1.vb)]
@@ -73,4 +73,4 @@ The *query string* is the portion of a URL beginning with a question mark (?) th
  Allow passing URL parameters to your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application only if you plan to cleanse the input of any malicious characters before using it. A string embedded with quotes, slashes, or semicolons, for example, might perform arbitrary data operations if used unfiltered in a SQL query against a database. For more information on query string security, see [Script exploits overview](https://msdn.microsoft.com/Library/772c7312-211a-4eb3-8d6e-eec0aa1dcc07).
 
 ## See also
-- [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)
+- [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)

docs/deployment/walkthrough-creating-a-custom-installer-for-a-clickonce-application.md

@@ -30,7 +30,7 @@ Any ClickOnce application based on an *.exe* file can be silently installed and
 
 2. Add a new class to your application and specify any name. This walkthrough uses the name `MyInstaller`.
 
-3. Add the following `Imports` or `using` statements to the top of your new class.
+3. Add the following `Imports` or `using` directives to the top of your new class.
 
     ```vb
     Imports System.Deployment.Application
@@ -71,4 +71,4 @@ Any ClickOnce application based on an *.exe* file can be silently installed and
 
 ## See also
 - [ClickOnce application manifest](../deployment/clickonce-application-manifest.md)
-- [\<entryPoint> element](../deployment/entrypoint-element-clickonce-application.md)
+- [\<entryPoint> element](../deployment/entrypoint-element-clickonce-application.md)

docs/extensibility/adding-a-shortcut-menu-in-a-tool-window.md

@@ -123,7 +123,7 @@ A shortcut menu such as the one shown in this walkthrough lets the user select f
 
 1. In *ShortcutMenu.cs*, the tool window can get the menu command service, but the control it contains cannot. The following steps show how to make the menu command service available to the user control.
 
-2. In *ShortcutMenu.cs*, add the following using statements:
+2. In *ShortcutMenu.cs*, add the following using directives:
 
     ```csharp
     using Microsoft.VisualStudio.Shell;
@@ -208,7 +208,7 @@ A shortcut menu such as the one shown in this walkthrough lets the user select f
     }
     ```
 
-8. Add the following using statements to the same file:
+8. Add the following using directives to the same file:
 
     ```csharp
     using Microsoft.VisualStudio.Shell;

docs/extensibility/adding-a-tool-window.md

@@ -13,6 +13,7 @@ ms.workload:
   - "vssdk"
 ---
 # Add a tool window
+
 In this walkthrough you learn how to create a tool window and integrate it into Visual Studio in the following ways:
 
 - Add a control to the tool window.
@@ -26,7 +27,8 @@ In this walkthrough you learn how to create a tool window and integrate it into
 - Set the default position for the tool window.
 
 ## Prerequisites
-Starting in Visual Studio 2015, you do not install the Visual Studio SDK from the download center. It is included as an optional feature in Visual Studio setup. You can also install the VS SDK later on. For more information, see [Install the Visual Studio SDK](../extensibility/installing-the-visual-studio-sdk.md).
+
+The Visual Studio SDK is included as an optional feature in Visual Studio setup. For more information, see [Install the Visual Studio SDK](../extensibility/installing-the-visual-studio-sdk.md).
 
 ## Create a tool window
 
@@ -84,7 +86,8 @@ By adding a toolbar in the following manner, you guarantee that its gradients an
     By setting the parent GUID and ID to the GUID and ID of the toolbar, you add the group to the toolbar.
 
 ## Add a command to the toolbar
- Add a command to the toolbar, which is displayed as a button.
+
+Add a command to the toolbar, which is displayed as a button.
 
 1. In the `<Symbols>` section, declare the following IDSymbol elements just after the toolbar and toolbar group declarations.
 
@@ -132,7 +135,7 @@ public System.Windows.Controls.MediaElement MediaPlayer
 ## Instantiate the tool window and toolbar
 Add a toolbar and a menu command that invokes the **Open File** dialog and plays the selected media file.
 
-1. Open *FirstToolWindow.cs* and add the following `using` statements.
+1. Open *FirstToolWindow.cs* and add the following `using` directives:
 
     ```csharp
     using System.ComponentModel.Design;
@@ -161,7 +164,7 @@ Add a toolbar and a menu command that invokes the **Open File** dialog and plays
     this.ToolBarLocation = (int)VSTWT_LOCATION.VSTWT_TOP;
     ```
 
-5. At this point the FirstToolWindow constructor should look like this:
+5. At this point, the FirstToolWindow constructor should look like this:
 
     ```csharp
     public FirstToolWindow() : base(null)
@@ -177,7 +180,7 @@ Add a toolbar and a menu command that invokes the **Open File** dialog and plays
     }
     ```
 
-6. Add the menu command to the toolbar. In the FirstToolWindowCommand.cs class, add the following using statement
+6. Add the menu command to the toolbar. In the FirstToolWindowCommand.cs class, add the following using directive:
 
     ```csharp
     using System.Windows.Forms;
@@ -243,7 +246,8 @@ Add a toolbar and a menu command that invokes the **Open File** dialog and plays
     ```
 
 ## Set the default position for the tool window
- Next, specify a default location in the IDE for the tool window. Configuration information for the tool window is in the *FirstToolWindowPackage.cs* file.
+
+Next, specify a default location in the IDE for the tool window. Configuration information for the tool window is in the *FirstToolWindowPackage.cs* file.
 
 1. In *FirstToolWindowPackage.cs*, find the <xref:Microsoft.VisualStudio.Shell.ProvideToolWindowAttribute> attribute on the `FirstToolWindowPackage` class, which passes the FirstToolWindow type to the constructor. To specify a default position, you must add more parameters to the constructor following example.
 

docs/extensibility/adding-search-to-a-tool-window.md

@@ -59,7 +59,7 @@ By following this walkthrough, you'll learn how to perform the following tasks:
     </StackPanel>
     ```
 
-3. In the *TestSearchControl.xaml.cs* file, add the following using statement:
+3. In the *TestSearchControl.xaml.cs* file, add the following using directive:
 
     ```csharp
     using System.Text;
@@ -102,7 +102,7 @@ By following this walkthrough, you'll learn how to perform the following tasks:
 ## To add the search implementation
  When you enable search on a <xref:Microsoft.VisualStudio.Shell.ToolWindowPane>, as in the previous procedure, the tool window creates a search host. This host sets up and manages search processes, which always occur on a background thread. Because the <xref:Microsoft.VisualStudio.Shell.ToolWindowPane> class manages the creation of the search host and the setting up of the search, you need only create a search task and provide the search method. The search process occurs on a background thread, and calls to the tool window control occur on the UI thread. Therefore, you must use the [ThreadHelper.Invoke*](https://msdn.microsoft.com/data/ee197798(v=vs.85)) method to manage any calls that you make in dealing with the control.
 
-1. In the *TestSearch.cs* file, add the following `using` statements:
+1. In the *TestSearch.cs* file, add the following `using` directives:
 
     ```csharp
     using System;
@@ -485,4 +485,4 @@ By following this walkthrough, you'll learn how to perform the following tasks:
 
 8. Choose the X on the right side of the search box.
 
-     The search is cleared, and the original contents appear. However, the **Match case** check box is still selected.
+     The search is cleared, and the original contents appear. However, the **Match case** check box is still selected.

docs/extensibility/creating-a-basic-project-system-part-1.md

@@ -184,7 +184,7 @@ Templates
 
 2. Add a class to the top *SimpleProject* folder named *SimpleProjectFactory.cs*.
 
-3. Add the following using statements:
+3. Add the following using directives:
 
    ```csharp
    using System.Runtime.InteropServices;
@@ -263,7 +263,7 @@ Templates
 
 ### To initialize the project factory
 
-1. In the *SimpleProjectPackage.cs* file, add the following `using` statement.
+1. In the *SimpleProjectPackage.cs* file, add the following `using` directive.
 
     ```csharp
     using Microsoft.VisualStudio.Project;
@@ -291,7 +291,7 @@ Templates
     }
     ```
 
-5. In *SimpleProjectFactory.cs*, add the following `using` statement after the existing `using` statements.
+5. In *SimpleProjectFactory.cs*, add the following `using` directive after the existing `using` directives.
 
     ```csharp
     using Microsoft.VisualStudio.Project;
@@ -410,7 +410,7 @@ Templates
 
 ### To connect the project factory class and the node class
 
-1. In the *SimpleProjectFactory.cs* file, add the following `using` statement:
+1. In the *SimpleProjectFactory.cs* file, add the following `using` directive:
 
     ```csharp
     using IOleServiceProvider =    Microsoft.VisualStudio.OLE.Interop.IServiceProvider;
@@ -454,7 +454,7 @@ Templates
 
 3. In the **Properties** window, change the **Build action** of the bitmap to **Embedded Resource**.
 
-4. In *SimpleProjectNode.cs*, add the following `using` statements:
+4. In *SimpleProjectNode.cs*, add the following `using` directives:
 
    ```csharp
    using System.Drawing;
@@ -556,7 +556,7 @@ Templates
 
 ### To substitute template parameters
 
-1. In the *SimpleProjectNode.cs* file, add the following `using` statement.
+1. In the *SimpleProjectNode.cs* file, add the following `using` directive.
 
    ```csharp
    using System.IO;
@@ -630,4 +630,4 @@ Templates
 
     ![Simple Project Command](../extensibility/media/simpleprojcommand.png "SimpleProjCommand")
 
-   Congratulations! You have implemented a basic managed project system.
+   Congratulations! You have implemented a basic managed project system.

docs/extensibility/dynamically-adding-menu-items.md

@@ -146,7 +146,7 @@ You can add menu items at run time by specifying the `DynamicItemStart` command
 
     ```
 
-2. Add the following using statements:
+2. Add the following using directives:
 
     ```csharp
     using Microsoft.VisualStudio.Shell;
@@ -206,7 +206,7 @@ You can add menu items at run time by specifying the `DynamicItemStart` command
     public const uint cmdidMyCommand = 0x104;
     ```
 
-2. In the *DynamicMenu.cs* file, add the following using statements:
+2. In the *DynamicMenu.cs* file, add the following using directives:
 
     ```csharp
     using EnvDTE;
@@ -352,4 +352,4 @@ public sealed class DynamicMenuItemsPackage : Package
 
 ## See also
 - [Commands, menus, and toolbars](../extensibility/internals/commands-menus-and-toolbars.md)
-- [How VSPackages add user interface elements](../extensibility/internals/how-vspackages-add-user-interface-elements.md)
+- [How VSPackages add user interface elements](../extensibility/internals/how-vspackages-add-user-interface-elements.md)

docs/extensibility/extending-the-properties-task-list-output-and-options-windows.md

@@ -55,7 +55,7 @@ You can access any tool window in Visual Studio. This walkthrough shows how to i
 
 ### Customize the constructor
 
-1. In the *TodoWindowControl.xaml.cs* file, add the following using statement:
+1. In the *TodoWindowControl.xaml.cs* file, add the following using directive:
 
     ```csharp
     using System;
@@ -97,7 +97,7 @@ You can access any tool window in Visual Studio. This walkthrough shows how to i
    }
    ```
 
-2. Add the following using statement:
+2. Add the following using directive:
 
    ```csharp
    using Microsoft.VisualStudio.Shell;
@@ -144,7 +144,7 @@ You can access any tool window in Visual Studio. This walkthrough shows how to i
 
      ![Properties Window](../extensibility/media/t5properties.png "T5Properties")
 
-2. Add the following using statements the *TodoItem.cs* file.
+2. Add the following using directives the *TodoItem.cs* file.
 
     ```csharp
     using System.ComponentModel;
@@ -277,7 +277,7 @@ You can access any tool window in Visual Studio. This walkthrough shows how to i
     }
     ```
 
-4. Add the following using statements to *TodoWindowControl.xaml.cs*:
+4. Add the following using directives to *TodoWindowControl.xaml.cs*:
 
     ```csharp
     using System.Runtime.InteropServices;

docs/extensibility/getting-project-properties.md

@@ -30,7 +30,7 @@ Starting in Visual Studio 2015, you do not install the Visual Studio SDK from th
 
 ### To display project properties in a tool window
 
-1. In the ProjectPropertiesToolWindowCommand.cs file, add the following using statements.
+1. In the ProjectPropertiesToolWindowCommand.cs file, add the following using directives.
 
     ```csharp
     using EnvDTE;
@@ -93,4 +93,4 @@ Starting in Visual Studio 2015, you do not install the Visual Studio SDK from th
 
 6. In the **View** > **Other Windows** click **ProjectPropertiesToolWindow**.
 
-  You should see the tree control in the tool window together with the name of the first project and of all its project properties.
+  You should see the tree control in the tool window together with the name of the first project and of all its project properties.

docs/extensibility/getting-service-information-from-the-settings-store.md

@@ -16,7 +16,7 @@ You can use the settings store to find all available services or to determine wh
 
 1. Create a VSIX project named `FindServicesExtension` and then add a custom command named `FindServicesCommand`. For more information about how to create a custom command, see [Create an extension with a menu command](../extensibility/creating-an-extension-with-a-menu-command.md)
 
-2. In *FindServicesCommand.cs*, add the following using statements:
+2. In *FindServicesCommand.cs*, add the following using directives:
 
     ```vb
     using System.Collections.Generic;
@@ -74,4 +74,4 @@ You can use the settings store to find all available services or to determine wh
 
 3. In the experimental instance, on the **Tools** menu, click **Invoke FindServicesCommand**.
 
-     You should see a message with the text **Help Service Available:**  followed by **True** or **False**. To verify this setting, you can use a registry editor, as shown in the earlier steps.
+     You should see a message with the text **Help Service Available:**  followed by **True** or **False**. To verify this setting, you can use a registry editor, as shown in the earlier steps.

docs/extensibility/how-to-provide-an-asynchronous-visual-studio-service.md

@@ -36,7 +36,7 @@ If you want to obtain a service without blocking the UI thread, you should creat
 
 5. The following example shows a very basic implementation of the three types. The constructor of the service class must set the service provider. In this example we'll just add the service to the package code file.
 
-6. Add the following using statements to the package file:
+6. Add the following using directives to the package file:
 
     ```csharp
     using System.Threading;
@@ -197,7 +197,7 @@ public sealed class TestAsyncPackage : AsyncPackage
 
 4. In the *TestAsyncCommand.cs* file, find the `MenuItemCallback()` method. Delete the body of the method.
 
-5. Add a using statement:
+5. Add a using directive:
 
     ```csharp
     using System.IO;