Merge pull request #2693 from MicrosoftDocs/master

8/7 AM Publish

Author: Taojunshen

docs/designers/getting-started-with-wpf.md

@@ -17,10 +17,10 @@ Windows Presentation Foundation (WPF) is a UI framework that creates desktop cli
 
 ## Where should I start?
 
-|||
+|Subject|Articles|
 |-|-|
 |I want to jump right in...|[Walkthrough: My first WPF desktop application](/dotnet/framework/wpf/getting-started/walkthrough-my-first-wpf-desktop-application)|
-| I want to compare XAML design tools... |[Design XAML in Visual Studio and Blend for Visual Studio](../designers/designing-xaml-in-visual-studio.md)|
+|I want to compare XAML design tools...|[Design XAML in Visual Studio and Blend for Visual Studio](../designers/designing-xaml-in-visual-studio.md)|
 |New to .NET?|[Overview of the .NET framework](/dotnet/framework/get-started/overview)<br /><br /> [Application Essentials](/dotnet/standard/application-essentials)<br /><br /> [Get Started with Visual C# and Visual Basic](../ide/getting-started-with-visual-csharp-and-visual-basic.md)|
 |Tell me more about WPF...|[Introduction to WPF](../designers/introduction-to-wpf.md)<br /><br /> [XAML overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf)<br /><br /> [Controls](/dotnet/framework/wpf/controls/)<br /><br /> [Data binding overview](/dotnet/framework/wpf/data/data-binding-overview)<br /><br /> [WPF data binding with LINQ to XML](../designers/wpf-data-binding-with-linq-to-xml-overview.md)|
 |Are you a Windows Forms developer?|[Windows Forms controls and equivalent WPF controls](/dotnet/framework/wpf/advanced/windows-forms-controls-and-equivalent-wpf-controls)<br /><br /> [Supported scenarios in WPF and Windows Forms interoperation](/dotnet/framework/wpf/advanced/wpf-and-windows-forms-interoperation)|

docs/designers/image-editor-examples.md

@@ -11,18 +11,15 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Image Editor Examples
+# Image Editor examples
 
 The articles in this section of the documentation contain examples that demonstrate how you can use the Image Editor.
 
-## Related topics
-
 |Title|Description|
 |-----------|-----------------|
 |[How to: Create a basic texture](../designers/how-to-create-a-basic-texture.md)|Demonstrates how to create a basic texture.|
-|[How to: Export a texture for use with Direct2D or Javascipt apps](../designers/how-to-export-a-texture-for-use-with-direct2d-or-javascipt-apps.md)|Demonstrates how to create a DDS-format texture that has premultiplied alpha that you can use in a Direct2D or WWA app.|
 |[How to: Create and modify MIP levels](../designers/how-to-create-and-modify-mip-levels.md)|Demonstrates how to generate MIP Levels from an image.|
-|[Using 3D assets in your game or app](../designers/using-3-d-assets-in-your-game-or-app.md)|Describes how you can use [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] to process 3D assets when you build your project or solution so that they are ready for use in your app. Strategies for loading different kinds of assets into your app are also discussed.|
+|[Using 3D assets in your game or app](../designers/using-3-d-assets-in-your-game-or-app.md)|Describes how you can use Visual Studio to process 3D assets when you build your project or solution so that they are ready for use in your app. Strategies for loading different kinds of assets into your app are also discussed.|
 |[How to: Export a texture that contains mipmaps](../designers/how-to-export-a-texture-that-contains-mipmaps.md)|Describes how to use the Image Content Pipeline to export a texture that contains precomputed mipmaps.|
 |[How to: Export a texture that has premultiplied alpha](../designers/how-to-export-a-texture-that-has-premultiplied-alpha.md)|Describes how to use the Image Content Pipeline to export a texture that contains premultiplied alpha values.|
 |[How to: Export a texture for use with Direct2D or Javascipt apps](../designers/how-to-export-a-texture-for-use-with-direct2d-or-javascipt-apps.md)|Describes how to use the Image Content Pipeline to export a texture that can be used in a Direct2D or Javascript App.|

docs/extensibility/verifying-subtypes-of-a-project-at-run-time.md

@@ -15,14 +15,14 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# Verifying Subtypes of a Project at Run Time
+# Verify subtypes of a project at run time
 A VSPackage that depends on a custom project subtype should include logic to look for that subtype so that it can fail gracefully if the subtype is not present. The following procedure shows how to verify the presence of a specified subtype.  
 
 ### To verify the presence of a subtype  
 
-1.  Obtain the project hierarchy from the project and solution objects as a <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> object by adding the following code to your VSPackage.  
+1.  Get the project hierarchy from the project and solution objects as a <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> object by adding the following code to your VSPackage.  
 
-    ```  
+    ```csharp  
     EnvDTE.DTE dte;  
     dte = (EnvDTE.DTE)Package.GetGlobalService(typeof(EnvDTE.DTE));  
 
@@ -39,22 +39,22 @@ A VSPackage that depends on a custom project subtype should include logic to loo
 
 2.  Cast the hierarchy to the <xref:Microsoft.VisualStudio.Shell.Flavor.IVsAggregatableProjectCorrected> interface.  
 
-    ```  
+    ```csharp  
     IVsAggregatableProjectCorrected AP;  
     AP = hierarchy as IVsAggregatableProjectCorrected;  
 
     ```  
 
 3.  Get the list of project type GUIDs by invoking the <xref:Microsoft.VisualStudio.Shell.Flavor.IVsAggregatableProjectCorrected.GetAggregateProjectTypeGuids%2A>.  
 
-    ```  
+    ```csharp  
     string projTypeGuids = AP.GetAggregateProjectTypeGuids().ToUpper();  
 
     ```  
 
 4.  Check the list for the GUID of the specified subtype.  
 
-    ```  
+    ```csharp  
     // Replace the string "MyGUID" with the GUID of the subtype.  
     string guidMySubtype = "MyGUID";  
     if (projTypeGuids.IndexOf(guidMySubtype) > 0)  
@@ -63,7 +63,7 @@ A VSPackage that depends on a custom project subtype should include logic to loo
     }  
     ```  
 
-## See Also  
- [Project Subtypes](../extensibility/internals/project-subtypes.md)   
- [Project Subtypes Design](../extensibility/internals/project-subtypes-design.md)   
- [Properties and Methods Extended by Project Subtypes](../extensibility/internals/properties-and-methods-extended-by-project-subtypes.md)
+## See also  
+ [Project subtypes](../extensibility/internals/project-subtypes.md)   
+ [Project subtypes design](../extensibility/internals/project-subtypes-design.md)   
+ [Properties and methods extended by project subtypes](../extensibility/internals/properties-and-methods-extended-by-project-subtypes.md)

docs/extensibility/visibilityconstraints-element.md

@@ -17,49 +17,49 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# VisibilityConstraints Element
+# VisibilityConstraints element
 The VisibilityConstraints element determines the static visibility of groups of commands and toolbars. The visibility is first controlled by the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] integrated development environment (IDE) without loading the VSPackage.  
 
 ## Syntax  
 
-```  
+```xml  
 <VisibilityConstraints>  
   <VisibilityConstraint>... </VisibilityConstraint>  
   <VisibilityConstraint>... </VisibilityConstraint>  
 </VisibilityConstraint>  
 ```  
 
-## Attributes and Elements  
+## Attributes and elements  
  The following sections describe attributes, child elements, and parent elements.  
 
 ### Attributes  
 
 |Attribute|Description|  
 |---------------|-----------------|  
-|Condition|Optional. See [Conditional Attributes](../extensibility/vsct-xml-schema-conditional-attributes.md).|  
+|Condition|Optional. See [Conditional attributes](../extensibility/vsct-xml-schema-conditional-attributes.md).|  
 
-### Child Elements  
+### Child elements  
 
 |Element|Description|  
 |-------------|-----------------|  
-|[VisibilityItem Element](../extensibility/visibilityitem-element.md)|Determines the static visibility of commands and toolbars.|  
+|[VisibilityItem element](../extensibility/visibilityitem-element.md)|Determines the static visibility of commands and toolbars.|  
 |[VisibilityConstraints](../extensibility/visibilityconstraints-element.md)|Determines the static visibility of groups of commands and toolbars.|  
 
-### Parent Elements  
+### Parent elements  
 
 |Element|Description|  
 |-------------|-----------------|  
-|[CommandTable Element](../extensibility/commandtable-element.md)|Defines all the elements that represent the commands (for example, menu items, menus, toolbars, and combo boxes) that a VSPackage provides to the IDE.|  
+|[CommandTable element](../extensibility/commandtable-element.md)|Defines all the elements that represent the commands (for example, menu items, menus, toolbars, and combo boxes) that a VSPackage provides to the IDE.|  
 
 ## Example  
 
-```  
+```xml  
 <VisibilityConstraints>  
   <VisibilityItem guid="cmdSetGuidMyProductCommands"     id="cmdidAddWidget"  
     context="guidNotViewSourceMode"/>  
 </VisibilityConstraints>  
 ```  
 
-## See Also  
- [VisibilityItem Element](../extensibility/visibilityitem-element.md)   
- [Visual Studio Command Table (.Vsct) Files](../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)
+## See also  
+ [VisibilityItem element](../extensibility/visibilityitem-element.md)   
+ [Visual Studio command table (.Vsct) files](../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)

docs/extensibility/visibilityitem-element.md

@@ -15,7 +15,7 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# VisibilityItem Element
+# VisibilityItem element
 The `VisibilityItem` element determines the static visibility of commands and toolbars. Every entry identifies a command or menu, and also an associated command UI context. Visual Studio detects commands, menus, and toolbars, and their visibility, without loading the VSPackages that define them. The IDE uses the <xref:Microsoft.VisualStudio.Shell.Interop.IVsMonitorSelection.IsCmdUIContextActive%2A> method to determine whether a command UI context is active.  
 
  After the VSPackage is loaded, Visual Studio expects command visibility to be determined by the VSPackage rather than the `VisibilityItem`. To determine your command's visibility, you can implement either the <xref:Microsoft.VisualStudio.Shell.OleMenuCommand.BeforeQueryStatus> event handler or the <xref:Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.QueryStatus%2A> method, depending on how you have implemented your command.  
@@ -26,14 +26,14 @@ The `VisibilityItem` element determines the static visibility of commands and to
 
 ## Syntax  
 
-```  
+```xml  
 <VisibilityItem  
   guid ="="cmdGuidMyProductCommands"  
   id=="cmdidAddWidget"  
   context="guidNotViewSourceMode"/>  
 ```  
   
-## Attributes and Elements  
+## Attributes and elements  
  The following sections describe attributes, child elements, and parent elements.  
   
 ### Attributes  
@@ -43,34 +43,34 @@ The `VisibilityItem` element determines the static visibility of commands and to
 |guid|Required. The GUID of the GUID/ID command identifier.|  
 |id|Required. The ID of the GUID/ID command identifier.|  
 |context|Required. The UI context in which the command is visible.|  
-|Condition|Optional. See [Conditional Attributes](../extensibility/vsct-xml-schema-conditional-attributes.md).|  
+|Condition|Optional. See [Conditional attributes](../extensibility/vsct-xml-schema-conditional-attributes.md).|  
   
-### Child Elements  
+### Child elements  
  None  
   
-### Parent Elements  
+### Parent elements  
   
 |Element|Description|  
 |-------------|-----------------|  
-|[VisibilityConstraints Element](../extensibility/visibilityconstraints-element.md)|The `VisibilityConstraints` element determines the static visibility of groups of commands and toolbars.|  
+|[VisibilityConstraints element](../extensibility/visibilityconstraints-element.md)|The `VisibilityConstraints` element determines the static visibility of groups of commands and toolbars.|  
   
 ## Remarks  
  The standard Visual Studio UI contexts are defined in the *Visual Studio SDK installation path*\VisualStudioIntegration\Common\Inc\vsshlids.h file as well as in the <xref:Microsoft.VisualStudio.Shell.Interop.UIContextGuids> and <xref:Microsoft.VisualStudio.Shell.Interop.UIContextGuids80> classes. A more complete set of UI contexts is defined in the <xref:Microsoft.VisualStudio.VSConstants> class.  
   
 ## Example  
   
-```  
+```xml  
 <VisibilityConstraints>  
   <VisibilityItem guid="cmdSetGuidMyProductCommands"     id="cmdidAddWidget"  
     context="guidNotViewSourceMode"/>  
 </VisibilityConstraints>  
 ```  
   
-## See Also  
+## See also  
  <xref:Microsoft.VisualStudio.Shell.Interop.IVsMonitorSelection.IsCmdUIContextActive%2A>   
  <xref:Microsoft.VisualStudio.Shell.OleMenuCommand.BeforeQueryStatus>   
  <xref:Microsoft.VisualStudio.VSConstants>   
  <xref:Microsoft.VisualStudio.Shell.Interop.UIContextGuids>   
  <xref:Microsoft.VisualStudio.Shell.Interop.UIContextGuids80>   
- [VisibilityConstraints Element](../extensibility/visibilityconstraints-element.md)   
- [Visual Studio Command Table (.Vsct) Files](../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)
+ [VisibilityConstraints element](../extensibility/visibilityconstraints-element.md)   
+ [Visual Studio command table (.Vsct) Files](../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)