changes after review input

Author: craigcaseyMSFT

docs/xml-tools/sorting-filtering-and-grouping-xml-schema-explorer.md

@@ -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.

docs/xml-tools/walkthrough-debug-an-xslt-style-sheet.md

@@ -94,7 +94,7 @@ The **XSL Output** window displays the output of the XSL transformation. This wi
 
 The following two files are used by the walkthrough.
 
-### *belowAvg.xsl*
+### belowAvg.xsl
 
 ```xml
 <?xml version='1.0'?>
@@ -117,7 +117,7 @@ The following two files are used by the walkthrough.
 </xsl:stylesheet>
 ```
 
-### *books.xml*
+### books.xml
 
 ```xml
 <?xml version='1.0'?>

docs/xml-tools/walkthrough-using-xml-editor-features.md

@@ -11,7 +11,7 @@ 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.
 
@@ -66,23 +66,23 @@ 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**.
 
      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 `>`.
 
@@ -104,7 +104,7 @@ The steps in this walkthrough show you how to create a new XML document. The wal
 
 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

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'?>