fixes

Author: v-thepet

docs/ide/adding-references-using-nuget-versus-an-extension-sdk.md

@@ -30,16 +30,16 @@ The following table helps you compare the referencing features of an SDK with th
 |Feature|SDK Support|SDK Notes|NuGet Support|NuGet Notes|
 |-------------|-----------------|---------------|-------------------|-----------------|
 |The mechanism references one entity and then all the files and functionality are available.|Y|You add an SDK by using the **Reference Manager** dialog box, and all the files and functionality are available during the development workflow.|Y||
-|MSBuild automatically consumes assemblies and Windows metadata (.winmd) files.|Y|References in the SDK are automatically passed to the compiler.|Y||
-|MSBuild automatically consumes the  .h or .lib files.|Y|The *SDKName.props* file tells Visual Studio how to set up the Visual C++ directory, and so forth, for automatic .h or .lib file consumption.|N||
-|MSBuild automatically consumes the  .js or .css files.|Y|In **Solution Explorer**, you can expand the JavaScript SDK reference node to show individual .js or .css files and then generate `<source include/>` tags by dragging those files to their source files. The SDK supports F5 and automatic package setup.|Y||
+|MSBuild automatically consumes assemblies and Windows metadata (*.winmd*) files.|Y|References in the SDK are automatically passed to the compiler.|Y||
+|MSBuild automatically consumes the  .h or .lib files.|Y|The *SDKName.props* file tells Visual Studio how to set up the Visual C++ directory, and so forth, for automatic *.h* or *.lib* file consumption.|N||
+|MSBuild automatically consumes the  *.js* or *.css* files.|Y|In **Solution Explorer**, you can expand the JavaScript SDK reference node to show individual *.js* or *.css* files and then generate `<source include/>` tags by dragging those files to their source files. The SDK supports F5 and automatic package setup.|Y||
 |MSBuild automatically adds the control in the **Toolbox**.|Y|The **Toolbox** can consume SDKs and show controls in the tabs that you specify.|N||
 |The mechanism supports Visual Studio Installer for extensions (VSIX).|Y|VSIX has a special manifest and logic to create SDK packages|Y|The VSIX can be embedded in another setup program.|
 |The **Object Browser** enumerates references.|Y|The **Object Browser** automatically gets the list of references in SDKs and enumerates them.|N||
 |Files and links automatically get added to  the **Reference Manager** dialog box (help links, and so forth auto populate)|Y|The **Reference Manager** dialog box automatically enumerates SDKs, along with help links and the list of SDK dependencies.|N|NuGet provides its own **Manage NuGet Packages** dialog box.|
 |The mechanism supports multiple architectures.|Y|SDKs can ship multiple configurations. MSBuild consumes the appropriate files for each project configuration.|N||
 |The mechanism supports multiple configurations.|Y|SDKs can ship multiple configurations. Depending on project architecture, MSBuild consumes the appropriate files for each project architecture.|N||
-|The mechanism can specify "not to copy."|Y|Depending on whether files are dropped in the \redist or \designtime folder, you can control which files to copy into the consuming application's package.|N|You declare which files to copy in the package manifest.|
+|The mechanism can specify "not to copy."|Y|Depending on whether files are dropped in the *\redist* or *\designtime* folder, you can control which files to copy into the consuming application's package.|N|You declare which files to copy in the package manifest.|
 |Content appears in localized files.|Y|Localized XML documents in SDKs are automatically included  for a better design-time experience.|N||
 |MSBuild supports consuming  multiple versions of an SDK simultaneously.|Y|The SDK supports consuming multiple versions simultaneously.|N|This isn't referencing. You can't have more than one version of NuGet files in your project at a time.|
 |The mechanism supports specifying applicable target frameworks, Visual Studio versions, and project types.|Y|The **Reference Manager** dialog box and the **Toolbox** show only the SDKs that apply to a project, so that users can more easily choose the appropriate SDKs.|Y (partial)|Pivot is the Target Framework. There is no filtering on user interface. At installation time, it might return an error.|
@@ -48,7 +48,7 @@ The following table helps you compare the referencing features of an SDK with th
 |The mechanism integrates with  [!INCLUDE[win8_appstore_long](../debugger/includes/win8_appstore_long_md.md)] concepts such as app manifest and Framework ID.|Y|The SDK must pass concepts that are specific to the [!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)] so that packaging and F5 work correctly with SDKs that are available in the[!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)].|N||
 |The mechanism  integrates with the app debugging pipeline for [!INCLUDE[win8_appname_long](../debugger/includes/win8_appname_long_md.md)] apps.|Y|The SDK must pass [!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)]-specific concepts so that packaging and F5 work correctly with SDKs available in the [!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)].|Y|NuGet content becomes part of the project. No special F5 consideration is needed.|
 |The mechanism integrates with app manifests.|Y|The SDK must pass [!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)]-specific concepts so that packaging and F5 work correctly with SDKs available in the [!INCLUDE[win8_appstore_short](../ide/includes/win8_appstore_short_md.md)].|Y|NuGet content becomes part of the project. No special F5 consideration is needed.|
-|The mechanism deploys non-reference files (for example, deploy test framework upon which to run tests of [!INCLUDE[win8_appname_long](../debugger/includes/win8_appname_long_md.md)] apps).|Y|If you drop the files in the \redist folder, the files are automatically deployed.|Y||
+|The mechanism deploys non-reference files (for example, deploy test framework upon which to run tests of [!INCLUDE[win8_appname_long](../debugger/includes/win8_appname_long_md.md)] apps).|Y|If you drop the files in the *\redist* folder, the files are automatically deployed.|Y||
 |The mechanism automatically adds the platform SDKs in Visual Studio IDE.|Y|If you drop the [!INCLUDE[win8](../debugger/includes/win8_md.md)] SDK or the Windows Phone SDK in a specific location with a specific layout, the SDK is automatically integrated with all the Visual Studio features.|N||
 |The mechanism supports a clean developer machine. (That is, no installation is required, and simple retrieval from source code control will work.)|N|Because you reference an SDK, you must check in your solution and the SDK separately. You can check in the SDK from the two non-registry default locations from which MSBuild iterates SDKs (for details, see [Creating a Software Development Kit](../extensibility/creating-a-software-development-kit.md)). As an alternative, if a custom location consists of the SDKs, you can specify the following code in the project file:<br /><br /> `<PropertyGroup>    <SDKReferenceDirectoryRoot>C:\MySDKs</SDKReferenceDirectoryRoot>   </PropertyGroup>`<br /><br /> Then check the SDKs into that location.|Y|You can check out the solution, and Visual Studio immediately recognizes and acts on the files.|
 |You can join a large existing community of package authors.|N/A|The community is new.|Y||
@@ -57,10 +57,10 @@ The following table helps you compare the referencing features of an SDK with th
 |The mechanism integrates with continuous-integration build servers for both package creation and consumption.|Y|The SDK must pass the checked-in location (SDKReferenceDirectoryRoot property) on command line to MSBuild.|Y||
 |The mechanism supports both stable and pre-release package versions.|Y|The SDK supports adding references to multiple versions.|Y||
 |The mechanism supports auto-update for installed packages.|Y|If shipped as VSIX or part of Visual Studio automatic updates, SDK provides automatic notifications.|Y||
-|The mechanism contains a stand-alone .exe file for creating and consuming packages.|Y|The SDK contains *MSBuild.exe*.|Y||
+|The mechanism contains a stand-alone *.exe* file for creating and consuming packages.|Y|The SDK contains *MSBuild.exe*.|Y||
 |Packages can be checked into version control.|Y|You can't check in anything outside the Documents node, which means that the Extension SDKs might not be checked in. The size of Extension SDK might be large.|Y||
 |You can use a PowerShell interface to create and consume packages.|Y (consumption), N (creation)|No tooling for creating an SDK. Consumption is executing MSBuild on the command line.|Y||
-|You can use a Symbol package for debugging support.|Y|If you drop .pdb files in the SDK, the files get picked up automatically.|Y||
+|You can use a Symbol package for debugging support.|Y|If you drop *.pdb* files in the SDK, the files get picked up automatically.|Y||
 |The mechanism supports package manager auto-updates.|N/A|The SDK gets revised with MSBuild.|Y||
 |The mechanism supports a lightweight manifest format.|Y|*SDKManifest.xml* supports many attributes, but a small subset is usually necessary.|Y||
 |The mechanism is available for  all Visual Studio editions.|Y|The SDK supports all Visual Studio editions.|Y|NuGet supports all Visual Studio editions.|

docs/ide/adding-visual-studio-editor-support-for-other-languages.md

@@ -68,17 +68,17 @@ All of these file types have  the features described earlier even if support for
 
  Add any new TextMate Grammars for Visual Studio in the following folder:  
 
- %userprofile%\\.vs\Extensions  
+ *%userprofile%\\.vs\Extensions*  
 
  Under this base path, add the following folder(s) if they apply to your situation:  
 
 |Folder Name|Description|  
 |-----------------|-----------------|  
-|\\*\<language name>*|The language folder. Replace *\<language name>* with the name of the language. For example, **\Matlab**.|  
-|\Syntaxes|The grammar folder. Contains the grammar .json files for the language, such as **Matlab.json**.|  
-|\Snippets|The snippets folder. Contains snippets for the language.|  
+|\\*\<language name>*|The language folder. Replace *\<language name>* with the name of the language. For example, *\Matlab*.|  
+|*\Syntaxes*|The grammar folder. Contains the grammar *.json* files for the language, such as *Matlab.json*.|  
+|*\Snippets*|The snippets folder. Contains snippets for the language.|  
 
- In Windows, %userprofile% resolves to the path: c:\Users\\*\<user name>*. If the extensions folder does not exist on your system, you will need to create it. If the folder already exists, it will be hidden.  
+ In Windows, *%userprofile%* resolves to the path: *c:\Users\\*\<user name>*.* If the extensions folder does not exist on your system, you will need to create it. If the folder already exists, it will be hidden.  
 
  For details about how to create TextMate Grammars, see [TextMate - Introduction to Language Grammars: How to add source code syntax highlighting embedded in HTML](https://developmentality.wordpress.com/2011/02/08/textmate-introduction-to-language-grammars/) and [Notes on how to create a Language Grammar and Custom Theme for a Textmate Bundle](https://benparizek.com/notebook/notes-on-how-to-create-a-language-grammar-and-custom-theme-for-a-textmate-bundle).  
 

docs/ide/building-and-cleaning-projects-and-solutions-in-visual-studio.md

@@ -36,7 +36,7 @@ By using the procedures in this topic, you can build, rebuild, or clean all or s
 > [!NOTE]
 > The UI in your edition of Visual Studio might differ from what this topic describes, depending on your active settings. To change your settings, for example to **General** or **Visual C++** settings, choose **Tools** > **Import and Export Settings**, and then choose **Reset all settings**.
   
-### To build, rebuild, or clean an entire solution  
+## To build, rebuild, or clean an entire solution  
 
 1.  In **Solution Explorer**, choose or open the solution.  
 
@@ -51,17 +51,17 @@ By using the procedures in this topic, you can build, rebuild, or clean all or s
 
     -   Choose **Clean Solution** to delete any intermediate and output files. With only the project and component files left, new instances of the intermediate and output files can then be built.  
 
-### To build or rebuild a single project  
+## To build or rebuild a single project  
 
 1.  In **Solution Explorer**, choose or open the project.  
 
-2.  On the menu bar, choose **Build**, and then choose either **Build***ProjectName* or **Rebuild***ProjectName*.  
+2.  On the menu bar, choose **Build**, and then choose either **Build*ProjectName*** or **Rebuild*ProjectName***.  
 
-    -   Choose **Build***ProjectName* to build only those project components that have changed since the most recent build.  
+    -   Choose **Build*ProjectName*** to build only those project components that have changed since the most recent build.  
 
-    -   Choose **Rebuild***ProjectName* to "clean" the project and then build the project files and all project components.  
+    -   Choose **Rebuild*ProjectName*** to "clean" the project and then build the project files and all project components.  
 
-### To build only the startup project and its dependencies  
+## To build only the startup project and its dependencies  
 
 1.  On the menu bar, choose **Tools** > **Options**.  
 
@@ -75,39 +75,39 @@ By using the procedures in this topic, you can build, rebuild, or clean all or s
 
     -   On the menu bar, choose **Debug** > **Start** (F5).  
 
-    -   On the menu bar, choose **Build** > **Build Solution** (CTRL+SHIFT+B).  
+    -   On the menu bar, choose **Build** > **Build Solution** (Ctrl+Shift+b).  
 
     When this check box is cleared, all projects, their dependencies, and the solution files are built when you run either of the preceding commands. By default, this check box is cleared.  
 
-### To build only the selected Visual C++ project  
+## To build only the selected Visual C++ project  
 
--  Choose a [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] project, and then, on the menu bar, choose **Build** > **Project Only**, and one of the following commands:  
+Choose a [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] project, and then, on the menu bar, choose **Build** > **Project Only**, and one of the following commands:  
+
+- **Build Only** *ProjectName*  
 
-    -   **Build Only** *ProjectName*  
-    
-    -   **Rebuild Only** *ProjectName*  
-    
-    -   **Clean Only** *ProjectName*  
-    
-    -   **Link Only** *ProjectName*  
+- **Rebuild Only** *ProjectName*  
 
-    These commands apply only to the [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] project that you chose, without building, rebuilding, cleaning, or linking any project dependencies or solution files. Depending on your version of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], the **Project Only** submenu might contain more commands.  
+- **Clean Only** *ProjectName*  
 
-### To compile multiple C++ project items  
+- **Link Only** *ProjectName*  
+
+These commands apply only to the [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] project that you chose, without building, rebuilding, cleaning, or linking any project dependencies or solution files. Depending on your version of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], the **Project Only** submenu might contain more commands.  
 
--  In **Solution Explorer**, choose multiple files that have can be compiled actions, open the shortcut menu for one of those files, and then choose **Compile**.  
+## To compile multiple C++ project items  
 
-    If the files have dependencies, the files will be compiled in dependency order. The compile operation will fail if the files require a precompiled header that isn't available when you compile. The compile operation uses the current active solution configuration.  
+In **Solution Explorer**, choose multiple files that have can be compiled actions, open the shortcut menu for one of those files, and then choose **Compile**.  
+
+If the files have dependencies, the files will be compiled in dependency order. The compile operation will fail if the files require a precompiled header that isn't available when you compile. The compile operation uses the current active solution configuration.  
 
-### To stop a build  
+## To stop a build  
 
-- Perform either of the following steps:  
+Perform either of the following steps:  
 
-    -   On the menu bar, choose **Build**, **Cancel**.  
-    
-    -   Choose the Ctrl + Break keys.  
+- On the menu bar, choose **Build** > **Cancel**.  
+  
+- Choose the Ctrl + Break keys.  
 
-### See also
+## See also
 
 [How to: View, save, and configure build log files](../ide/how-to-view-save-and-configure-build-log-files.md)  
 [Obtaining build logs](../msbuild/obtaining-build-logs-with-msbuild.md)  

docs/ide/common-quick-actions.md

@@ -171,9 +171,9 @@ End Function
 
 ## Actions that remove unnecessary code
 
-### Remove unnecesary usings/imports
+### Remove unnecessary usings/Imports
 
-The **Remove Unnecessary Usings/Imports** Quick Action will remove any unused `using` and `import` statements for the current file.  When you select this item, unused namespace imports will be immediately removed.
+The **Remove Unnecessary Usings/Imports** Quick Action will remove any unused `using` and `Import` statements for the current file.  When you select this item, unused namespace imports will be immediately removed.
 
 |  Applicable Languages |  Supported Version |
 |  -------------------- | ----------------  |

docs/ide/compiling-and-building-in-visual-studio.md

@@ -40,7 +40,7 @@ The documentation in this section goes into further details of the IDE-based bui
 
 ## Overview of building from the IDE  
 
-When you create a project, Visual Studio created default build configurations for the project and the solution that contains the project.  These configurations define how the solutions and projects are built and deployed. Project configurations in particular are unique for a target platform (such as Windows pr Linux) and build type (such as debug or release). You can edit these configurations however you like, and can also create your own configurations as needed.
+When you create a project, Visual Studio created default build configurations for the project and the solution that contains the project.  These configurations define how the solutions and projects are built and deployed. Project configurations in particular are unique for a target platform (such as Windows or Linux) and build type (such as debug or release). You can edit these configurations however you like, and can also create your own configurations as needed.
 
 For a first introduction to building within the IDE, see [Walkthrough: Building an application](walkthrough-building-an-application.md).  
 

docs/ide/create-a-visual-basic-winform-in-visual-studio.md

@@ -45,9 +45,9 @@ After you select your Visual Basic project template and name your file, Visual S
 
      ![Click the Toolbox to open the Toolbox window](../ide/media/vb-toolbox-toolwindow.png)  
 
-     (If you don't see the Toolbox fly-out option, you can open it from the menu bar. To do so, click **View** > **Toolbox**. Or, press **Ctrl**+**Alt**+**X**.)
+     (If you don't see the **Toolbox** fly-out option, you can open it from the menu bar. To do so, click **View** > **Toolbox**. Or, press **Ctrl**+**Alt**+**X**.)
 
-2. Click the **Pin** icon to dock the Toolbox window.
+2. Click the **Pin** icon to dock the **Toolbox** window.
 
      ![Click the Pin icon to pin the Toolbox window to the IDE](../ide/media/vb-pin-the-toolbox-window.png)  
 3. Click the **Button** control and then drag it onto the form.
@@ -58,7 +58,7 @@ After you select your Visual Basic project template and name your file, Visual S
 
      ![Add text to the button on the form](../ide/media/vb-button-control-text.png)  
 
-     (If you don't see the Properties window, you can open it from the menu bar. To do so, click **View** > **Properties Window**. Or, press **F4**.)
+     (If you don't see the **Properties** window, you can open it from the menu bar. To do so, click **View** > **Properties Window**. Or, press **F4**.)
 
 5. In the **Design** section of the **Properties** window, change the name from **Button1** to `btnClickThis`, and then press **Enter**.