USMT code blocks standarization

windows/deployment/usmt/understanding-migration-xml-files.md

@@ -164,7 +164,7 @@ You can use multiple XML files with the ScanState and LoadState tools. Each of t
 
 For example, you can use all of the XML migration file types for a single migration, as in the following example:
 
-``` syntax
+```cmd
 ScanState.exe <store> /config:c:\myFolder\Config.xml /i:migapps.xml /i:MigDocs.xml /i:CustomRules.xml
 ```
 
@@ -194,14 +194,14 @@ To generate the XML migration rules file for a source computer:
 
 4. At the command prompt, enter:
 
-    ``` syntax
+    ```cmd
     cd /d <USMTpath>
     ScanState.exe /genmigxml: <filepath.xml>
     ```
 
     Where *&lt;USMTpath&gt;* is the location on your source computer where you've saved the USMT files and tools, and *&lt;filepath.xml&gt;* is the full path to a file where you can save the report. For example, enter:
 
-    ``` syntax
+    ```cmd
     cd /d c:\USMT
     ScanState.exe /genmigxml:"C:\Documents and Settings\USMT Tester\Desktop\genMig.xml"
     ```
@@ -230,13 +230,13 @@ The `MigDocs.xml` file calls the `GenerateDocPatterns` function, which takes thr
 
 **Usage:**
 
-``` syntax
+```cmd
 MigXmlHelper.GenerateDocPatterns ("<ScanProgramFiles>", "<IncludePatterns>", "<SystemDrive>")
 ```
 
 To create include data patterns for only the system drive:
 
-``` xml
+```xml
 <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
      <objectSet>
         <script>MigXmlHelper.GenerateDocPatterns ("FALSE","TRUE","TRUE")</script>
@@ -246,7 +246,7 @@ To create include data patterns for only the system drive:
 
 To create an include rule to gather files for registered extensions from the %PROGRAMFILES% directory:
 
-``` xml
+```xml
 <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
      <objectSet>
         <script>MigXmlHelper.GenerateDocPatterns ("TRUE","TRUE","FALSE")</script>
@@ -256,7 +256,7 @@ To create an include rule to gather files for registered extensions from the %PR
 
 To create exclude data patterns:
 
-``` xml
+```xml
 <exclude filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
      <objectSet>
         <script>MigXmlHelper.GenerateDocPatterns ("FALSE","FALSE","FALSE")</script>
@@ -339,7 +339,7 @@ To exclude the new text document.txt file and any .txt files in "new folder", yo
 
 To exclude Rule 1, there needs to be an exact match of the file name. However, for Rule 2, you can create a pattern to exclude files by using the file name extension.
 
-``` xml
+```xml
 <exclude>
      <objectSet>
         <pattern type="File">D:\Newfolder\[new text document.txt]</pattern>
@@ -352,7 +352,7 @@ To exclude Rule 1, there needs to be an exact match of the file name. However, f
 
 If you don't know the file name or location of the file, but you do know the file name extension, you can use the `GenerateDrivePatterns` function. However, the rule will be less specific than the default include rule generated by the `MigDocs.xml` file, so it will not have precedence. You must use the &lt;UnconditionalExclude&gt; element to give this rule precedence over the default include rule. For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md).
 
-``` xml
+```xml
 <unconditionalExclude>
      <objectSet>
         <script>MigXmlHelper.GenerateDrivePatterns ("*[*.txt]", "Fixed")</script>
@@ -364,7 +364,7 @@ If you don't know the file name or location of the file, but you do know the fil
 
 If you want the **&lt;UnconditionalExclude&gt;** element to apply to both the system and user context, you can create a third component using the **UserandSystem** context. Rules in this component will be run in both contexts.
 
-``` xml
+```xml
 <component type="Documents" context="UserandSystem">
    <displayName>MigDocExcludes</displayName>
    <role role="Data">
@@ -389,7 +389,7 @@ The application data directory is the most common location that you would need t
 
 This rule will include .pst files that are located in the default location, but aren't linked to Microsoft Outlook. Use the user context to run this rule for each user on the computer.
 
-``` xml
+```xml
 <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
      <objectSet>
         <pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Outlook\*[*.pst]</pattern>
@@ -401,7 +401,7 @@ This rule will include .pst files that are located in the default location, but
 
 For locations outside the user profile, such as the Program Files folder, you can add the rule to the system context component.
 
-``` xml
+```xml
 <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
      <objectSet>
         <pattern type="File">%CSIDL_PROGRAM_FILES%\*[*.pst]</pattern>