Merge pull request #2145 from craigcaseyMSFT/vcraic0601e

TrishaMc · web-flow · commit ba94f75fb2a8 · 2018-05-31T09:29:36.000-07:00
Content update project in xml tools folder (41-50)
diff --git a/docs/xml-tools/sorting-filtering-and-grouping-xml-schema-explorer.md b/docs/xml-tools/sorting-filtering-and-grouping-xml-schema-explorer.md
@@ -11,11 +11,11 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Sorting, Filtering, and Grouping (XML Schema Explorer)
+# Sorting, filtering, and grouping (XML Schema Explorer)
 
-This topic describes the options that are available through the **Sorting, Filtering, and Grouping Options** menu on the XML Schema Explorer toolbar.
+This topic describes the options that are available through the **Sorting, Filtering, and Grouping Options** menu on the **XML Schema Explorer** toolbar.
 
-## Filter Options
+## Filter options
 
  The following filter options are available. By default, the **Show Namespaces** and **Show Schema Files** options are selected.
 
@@ -25,9 +25,9 @@ This topic describes the options that are available through the **Sorting, Filte
 
 -   **Show Compositors (sequence/choice/all)**.
 
-## Sorting Options
+## Sorting options
 
- The following sorting options are available. The default is **Sort By Type**. Sort By options do not apply to files and namespaces.
+ The following sorting options are available. The default is **Sort By Type**. **Sort By** options do not apply to files and namespaces.
 
 -   **Sort By Type**.
 
@@ -73,6 +73,6 @@ This topic describes the options that are available through the **Sorting, Filte
 
  The **Document Order** option is available when the **Show Schema Files** option is selected. When **Document Order** is selected, global nodes are displayed in the order in which they appear in the schema file.
 
-## Persisting Sort/Filter Options
+## Persisting sort/filter options
 
  The sorting, filtering, and grouping options are saved to the registry for each user, no matter which solution or files were open when the settings were changed.
diff --git a/docs/xml-tools/walkthrough-debug-an-xslt-style-sheet.md b/docs/xml-tools/walkthrough-debug-an-xslt-style-sheet.md
@@ -11,7 +11,7 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Walkthrough: Debug an XSLT Style Sheet
+# Walkthrough: Debug an XSLT style sheet
 
 The steps in this walkthrough demonstrate how to use the XSLT debugger. Steps include viewing variables, setting breakpoints, and stepping through the code. The style sheet finds all books that cost below the average book price.
 
@@ -21,19 +21,19 @@ The steps in this walkthrough demonstrate how to use the XSLT debugger. Steps in
 
 2.  Copy the two sample files to your local computer.
 
-## Start Debugging
+## Start debugging
 
 ### To start debugging
 
 1.  From the **File** menu, point to **Open**, and click **File**.
 
-2.  Locate the belowAvg.xsl file and click **Open**.
+2.  Locate the *belowAvg.xsl* file and click **Open**.
 
      The style sheet is opened in the XML Editor.
 
 3.  Click the browse button (**...**) on the **Input** field of the document properties window.
 
-4.  Locate the books.xml file and click **Open**.
+4.  Locate the *books.xml* file and click **Open**.
 
      This sets the source document file that is used for the XSLT transformation.
 
@@ -43,54 +43,54 @@ The steps in this walkthrough demonstrate how to use the XSLT debugger. Steps in
 
 This starts the debugging process and opens several new windows that are used by the debugger.
 
-There are two windows that display the input document and styles sheet. The debugger uses these windows to show the current execution state. The debugger is positioned on the `xsl:if` element of the style sheet and on the first book node in the books.xml file.
+There are two windows that display the input document and styles sheet. The debugger uses these windows to show the current execution state. The debugger is positioned on the `xsl:if` element of the style sheet and on the first book node in the *books.xml* file.
 
-The Locals window displays all the local variables and their current values. This includes variables defined in the style sheet and also variables that the debugger uses to track the nodes that are currently in context.
+The **Locals** window displays all the local variables and their current values. This includes variables defined in the style sheet and also variables that the debugger uses to track the nodes that are currently in context.
 
 The **XSL Output** window displays the output of the XSL transformation. This window is separate from the **Visual Studio Output** window.
 
-## Watch Window
+## Watch window
 
 ### To use the Watch window
 
 1.  From the **Debug** menu, point to **Windows**, point to **Watch**, and click **Watch 1**.
 
-     This makes the Watch 1 window visible.
+     This makes the **Watch 1** window visible.
 
-2.  Type `$bookAverage` in the **Name** field and press ENTER.
+2.  Type `$bookAverage` in the **Name** field and press **Enter**.
 
      The value of the `$bookAverage` variable is displayed in the window.
 
-3.  Type `self::node()` in the **Name** field and press ENTER.
+3.  Type `self::node()` in the **Name** field and press **Enter**.
 
      `self::node()` is an XPath expression that evaluates to the current context node. The value of the `self::node()` XPath expression is the first book node. This changes as we progress through the transformation.
 
 4.  Expand the `self::node()` node, and then expand the `price` node.
 
      This allows you to see the value of the book price and you can easily compare it to the `$bookAverage` value. Because the book price is below the average, the `xsl:if` condition should succeed.
 
-## Step Through the Code
+## Step through the code
  The debugger enables you to execute code one line at a time.
 
 ### To step through the code
 
 1.  Press **F5** to continue.
 
-     Because the first book node satisfied the `xsl:if` condition, the book node is added to the XSL output window. The debugger continues to execute until it is positioned again on the `xsl:if` element in the style sheet. The debugger is now positioned on the second book node in the books.xml file.
+     Because the first book node satisfied the `xsl:if` condition, the book node is added to the **XSL Output** window. The debugger continues to execute until it is positioned again on the `xsl:if` element in the style sheet. The debugger is now positioned on the second book node in the *books.xml* file.
 
-     In the Watch1 window the `self::node()` value changes to the second book node. By examining the value of the price element, you can determine that the price is above the average, thus the `xsl:if` condition should fail.
+     In the **Watch 1** window the `self::node()` value changes to the second book node. By examining the value of the price element, you can determine that the price is above the average, thus the `xsl:if` condition should fail.
 
 2.  Press **F5** to continue.
 
-     Because the second book node does not meet the `xsl:if` condition, the book node is not added to the XSL output window. The debugger continues to execute until it is positioned again on the `xsl:if` element in the style sheet. The debugger is now positioned on the third `book` node in the books.xml file.
+     Because the second book node does not meet the `xsl:if` condition, the book node is not added to the **XSL Output** window. The debugger continues to execute until it is positioned again on the `xsl:if` element in the style sheet. The debugger is now positioned on the third `book` node in the *books.xml* file.
 
-     In the Watch1 window the `self::node()` value changes to the third book node. By examining the value of the `price` element, you can determine that the price is below the average, thus the `xsl:if` condition should succeed.
+     In the **Watch 1** window the `self::node()` value changes to the third book node. By examining the value of the `price` element, you can determine that the price is below the average, thus the `xsl:if` condition should succeed.
 
 3.  Press **F5** to continue.
 
-     Because the `xsl:if` condition was satisfied, the third book is added to the XSL Output window. All books in the XML document have been processed and the debugger stops.
+     Because the `xsl:if` condition was satisfied, the third book is added to the **XSL Output** window. All books in the XML document have been processed and the debugger stops.
 
-## Sample Files
+## Sample files
 
 The following two files are used by the walkthrough.
 
@@ -149,6 +149,6 @@ The following two files are used by the walkthrough.
 </bookstore>
 ```
 
-## See Also
+## See also
 
 - [Debugging XSLT](../xml-tools/debugging-xslt.md)
diff --git a/docs/xml-tools/walkthrough-using-xml-editor-features.md b/docs/xml-tools/walkthrough-using-xml-editor-features.md
@@ -11,14 +11,14 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# Walkthrough: Using XML Editor Features
+# Walkthrough: Use XML editor features
 
 The steps in this walkthrough show you how to create a new XML document. The walkthrough also uses some of the features of the XML Editor that make it valuable for XML authoring.
 
 > [!NOTE]
-> Before starting the walkthrough, save the hireDate.xsd file (included below in this topic) to your local computer.
+> Before starting the walkthrough, save the *hireDate.xsd* file (included below in this topic) to your local computer.
 
-## To create a new XML file and associate it with an XML Schema
+## To create a new XML file and associate it with an XML schema
 
 1.  On the **File** menu, point to **New**, and click **File**.
 
@@ -34,7 +34,7 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 
      The **Open XSD Schema** dialog box is displayed.
 
-5.  Select the hireDate.xsd file and click **Open**.
+5.  Select the *hireDate.xsd* file and click **Open**.
 
 6.  Click **OK**.
 
@@ -54,7 +54,7 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 
     -   **employee** to add the root element.
 
-2.  Select **<!--** to add a comment node and press ENTER.
+2.  Select **<!--** to add a comment node and press **Enter**.
 
      The editor inserts a comment end tag and places the cursor between the start and end comment tags.
 
@@ -66,25 +66,25 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 
 5.  Type `>` to close the tag.
 
-6.  The editor adds the end tag. The end tag is added with a wavy underline indicating a validation error. The ToolTip displays the message: The element 'employee' has incomplete content. Expected 'ID'.
+6.  The editor adds the end tag. The end tag is added with a wavy underline indicating a validation error. The **ToolTip** displays the message: **The element 'employee' has incomplete content. Expected 'ID'**.
 
 7.  Type `<` and select **ID** from the member list. Then type `>`.
 
      The editor adds the XML element, `<ID></ID>`, and positions the cursor after the ID start tag.
 
 8.  Type **abc**.
 
-     The **abc** text has a wavy underline. The ToolTip displays the message: The 'ID' element has an invalid value according to its data type.
+     The **abc** text has a wavy underline. The **ToolTip** displays the message: **The 'ID' element has an invalid value according to its data type**.
 
-9. Right click on the ID element and select **Go To Definition**.
+9. Right-click on the ID element and select **Go To Definition**.
 
-     The editor opens the hireDate.xsd file in a new document window and positions the cursor on the ID schema element definition.
+     The editor opens the *hireDate.xsd* file in a new document window and positions the cursor on the ID schema element definition.
 
 10. Return to the XML file, and replace the **abc** text with **123**.
 
-     The wavy underline and ToolTip are cleared under the ID element value. The ToolTip for the employee end tag now displays the message: The element 'employee' has incomplete content. Expected 'hire-date'.
+     The wavy underline and **ToolTip** are cleared under the ID element value. The **ToolTip** for the employee end tag now displays the message: **The element 'employee' has incomplete content. Expected 'hire-date'**.
 
-11. Place the cursor after the ID end tag, type in `<`, select hire-date from the member list, and then type in `>`.
+11. Place the cursor after the ID end tag, type in `<`, select **hire-date** from the member list, and then type in `>`.
 
      The editor adds the XML element, `<hire-date></hire-date>`, and positions the cursor after the hire-date start tag.
 
@@ -100,11 +100,11 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 
 1.  From the **File** menu, select **Save As**.
 
-     The **Save File As** dialog box is displayed. The default filename is 'XMLFile1'.
+     The **Save File As** dialog box is displayed. The default filename is *'XMLFile1'*.
 
 2.  Enter the file name and location for the XML document and click **Save**.
 
-## hireDate.xsd File
+## hireDate.xsd file
  The following schema file is used by the walkthrough.
 
 ```xml
@@ -123,6 +123,6 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 </xs:schema>
 ```
 
-## See Also
+## See also
 
 - [XML Editor](../xml-tools/xml-editor.md)
diff --git a/docs/xml-tools/walkthrough-using-xslt-hierarchy.md b/docs/xml-tools/walkthrough-using-xslt-hierarchy.md
@@ -8,7 +8,7 @@ author: gewarren
 ms.author: gewarren
 manager: douge
 ---
-# Walkthrough: Using XSLT Hierarchy
+# Walkthrough: Use XSLT hierarchy
 
 The XSLT Hierarchy tool simplifies many XML development tasks. An XSLT style sheet often uses `includes` and `imports` instructions. Compilation starts from the principal style sheet, but when you see an error as a result of compiling an XSLT style sheet, the error may come from a different source than the principal style sheet. Fixing the error or editing the style sheet may require access to included or imported style sheets. Stepping through the style sheet in the debugger may open included and imported style sheets, and you may want to add a breakpoint at some point in one or more of the included style sheets.
 
@@ -42,7 +42,7 @@ The example in this topic demonstrates debugging in a referenced style sheet.
     </COLLECTION>
     ```
 
-1. Add the following `xslincludefile.xsl`:
+1. Add the following *xslincludefile.xsl*:
 
     ```xml
     <?xml version='1.0'?>
@@ -65,7 +65,7 @@ The example in this topic demonstrates debugging in a referenced style sheet.
     </xsl:stylesheet>
     ```
 
-3.  Add the following `xslinclude.xsl` file:
+3.  Add the following *xslinclude.xsl* file:
 
     ```xml
     <?xml version='1.0'?>
@@ -107,4 +107,4 @@ The example in this topic demonstrates debugging in a referenced style sheet.
 
 ## See also
 
-- [Walkthrough: XSLT Profiler](../xml-tools/walkthrough-xslt-profiler.md)
+- [Walkthrough: XSLT profiler](../xml-tools/walkthrough-xslt-profiler.md)
diff --git a/docs/xml-tools/walkthrough-using-xslt-intellisense.md b/docs/xml-tools/walkthrough-using-xslt-intellisense.md
@@ -41,7 +41,7 @@ This walkthrough demonstrates how to use XSLT IntelliSense to auto-complete valu
     </xsl:stylesheet>
     ```
 
-2.  Insert your cursor after `<xsl:template name="msg23" match="msg23">` and press ENTER. Then start typing the following `xsl:call-template` element:
+2.  Insert your cursor after `<xsl:template name="msg23" match="msg23">` and press **Enter**. Then start typing the following `xsl:call-template` element:
 
     ```xml
     <xsl:call-template name="localized-message">
@@ -50,7 +50,7 @@ This walkthrough demonstrates how to use XSLT IntelliSense to auto-complete valu
 
      The list of template names appears in the `name=""` attribute of the `xsl:call-template` element as you type.
 
-3.  Insert your cursor after `<xsl:call-template name="localized-message">` and press ENTER. Then start typing the following `xsl:with-param` element:
+3.  Insert your cursor after `<xsl:call-template name="localized-message">` and press **Enter**. Then start typing the following `xsl:with-param` element:
 
     ```xml
     <xsl:with-param name="msgcode">msg23</xsl:with-param>
@@ -107,7 +107,7 @@ This walkthrough demonstrates how to use XSLT IntelliSense to auto-complete valu
     </xsl:stylesheet>
     ```
 
-2.  Insert your cursor  after `<xsl:apply-templates select="phone" />` and press ENTER. Then start typing the following `xsl: apply-templates` element:
+2.  Insert your cursor  after `<xsl:apply-templates select="phone" />` and press **Enter**. Then start typing the following `xsl: apply-templates` element:
 
     ```xml
     <xsl:apply-templates select="phone"  mode="accountNumber">
@@ -148,7 +148,7 @@ This walkthrough demonstrates how to use XSLT IntelliSense to auto-complete valu
     </xsl:stylesheet>
     ```
 
-2.  Insert your cursor after `<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:alt="http://www.w3.org/1999/XSL/Transform-alternate" version="1.0">` and press ENTER. Then start typing the following `xsl:namespace-alias` element:
+2.  Insert your cursor after `<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:alt="http://www.w3.org/1999/XSL/Transform-alternate" version="1.0">` and press **Enter**. Then start typing the following `xsl:namespace-alias` element:
 
     ```xml
     <xsl:namespace-alias stylesheet-prefix="alt" result-prefix="xsl"/>
@@ -158,4 +158,4 @@ This walkthrough demonstrates how to use XSLT IntelliSense to auto-complete valu
 
 ## See also
 
-- [XML Editor IntelliSense Features](../xml-tools/xml-editor-intellisense-features.md)
+- [XML Editor IntelliSense features](../xml-tools/xml-editor-intellisense-features.md)
diff --git a/docs/xml-tools/walkthrough-xslt-profiler.md b/docs/xml-tools/walkthrough-xslt-profiler.md
@@ -83,7 +83,7 @@ The procedures in the following walkthrough require Visual Studio and .NET Frame
 
 5.  You can also sort the data by clicking column names.
 
-### Select CallTree view
+### Select Call Tree View
 
 1.  Select **Call Tree View** in the **Current View** drop-down list. This view is a tree view of program execution.
 
@@ -103,6 +103,6 @@ The procedures in the following walkthrough require Visual Studio and .NET Frame
 
 4.  The process view displays a table that includes the **Process ID**, **Process Name**, **Begin Time**, and the **End Time**. Data can be sorted by clicking column names.
 
-## See Also
+## See also
 
-- [Walkthrough: Using XSLT Hierarchy](../xml-tools/walkthrough-using-xslt-hierarchy.md)
+- [Walkthrough: Using XSLT hierarchy](../xml-tools/walkthrough-using-xslt-hierarchy.md)
diff --git a/docs/xml-tools/working-with-xml-data.md b/docs/xml-tools/working-with-xml-data.md
@@ -30,7 +30,7 @@ Additional features include:
 
 - Support for editing XSLT style sheets, including IntelliSense support.
 
-- XML Schema Explorer.
+- **XML Schema Explorer**.
 
 ## XML Schema designer
 
@@ -45,15 +45,15 @@ Visual Studio supports debugging XSLT style sheets. Using the debugger, you can
 [Debugging XSLT](../xml-tools/debugging-xslt.md)
 Discusses how to debug style sheets using the Visual Studio debugger.
 
-[XML Standards Reference](http://msdn.microsoft.com/79c78508-c9d0-423a-a00f-672e855de401)
+[XML standards reference](http://msdn.microsoft.com/79c78508-c9d0-423a-a00f-672e855de401)
 Provides information about XML technologies, including XML, Document Type Definition (DTD), XML Schema definition language (XSD), and XSLT.
 
 [Create and configure datasets in Visual Studio](../data-tools/create-and-configure-datasets-in-visual-studio.md)
 Provides an explanation of the design-time tools for creating datasets.
 
-[XML Web Services in Managed Code](http://msdn.microsoft.com/c9a7dc25-3e68-4723-bfb7-de4320830196)
+[XML Web services in managed code](http://msdn.microsoft.com/c9a7dc25-3e68-4723-bfb7-de4320830196)
 Discusses how to create and deploy XML Web services and how to access XML Web services.
 
 ## See also
 
-- [XML Tools in Visual Studio](../xml-tools/xml-tools-in-visual-studio.md)
+- [XML tools in Visual Studio](../xml-tools/xml-tools-in-visual-studio.md)
diff --git a/docs/xml-tools/xml-document-properties-properties-window.md b/docs/xml-tools/xml-document-properties-properties-window.md
diff --git a/docs/xml-tools/xml-document-validation.md b/docs/xml-tools/xml-document-validation.md
diff --git a/docs/xml-tools/xml-editor.md b/docs/xml-tools/xml-editor.md
