fix: Replace syntax with langauge code 2

windows/configuration/customize-and-export-start-layout.md

@@ -176,7 +176,7 @@ If the Start layout is applied by Group Policy or MDM, and the policy is removed
 2.  [Export the Start layout](#export-the-start-layout).
 3.  Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
 
-    ``` syntax
+    ```xml
     <DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
     ```
 

windows/configuration/mobile-devices/settings-that-can-be-locked-down.md

@@ -462,7 +462,7 @@ Quick action buttons are locked down in exactly the same way as Settings pages/g
 
 You can specify the quick actions as follows:
 
-``` syntax
+```xml
 <Settings>
     <System name="QuickActions_Launcher_AllSettings" />
     <System name="QuickActions_Launcher_DeviceDiscovery" />

windows/configuration/ue-v/uev-application-template-schema-reference.md

@@ -241,7 +241,7 @@ Version identifies the version of the settings location template for administrat
 
 **Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
 
-``` syntax
+```xml
   <!--
      Version History
 
@@ -280,7 +280,7 @@ Author identifies the creator of the settings location template. Two optional ch
 
 Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
 
-``` syntax
+```xml
     <Process>
       <Filename>MyApplication.exe</Filename>
       <Architecture>Win64</Architecture>
@@ -355,7 +355,7 @@ UE-V does not support ARM processors in this version.
 
 ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
 
-``` syntax
+```xml
     <Process>
       <Filename>MyApplication.exe</Filename>
       <ProductName>My Application 6.x by Contoso.com</ProductName>
@@ -375,7 +375,7 @@ FileDescription is an optional tag that allows for an administrative description
 
 For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
 
-``` syntax
+```xml
 <Processes>
 
    <Process>
@@ -409,7 +409,7 @@ The product and file version elements may be left unspecified. Doing so makes th
 
 Product version: 1.0 specified in the UE-V template generator produces the following XML:
 
-``` syntax
+```xml
       <ProductVersion>
         <Major Minimum="1" Maximum="1" />
         <Minor Minimum="0" Maximum="0" />
@@ -420,7 +420,7 @@ Product version: 1.0 specified in the UE-V template generator produces the follo
 
 File version: 5.0.2.1000 specified in the UE-V template generator produces the following XML:
 
-``` syntax
+```xml
       <FileVersion>
         <Major Minimum="5" Maximum="5" />
         <Minor Minimum="0" Maximum="0" />
@@ -433,7 +433,7 @@ File version: 5.0.2.1000 specified in the UE-V template generator produces the f
 
 Only the Minimum attribute is present. Maximum must be included in a range as well.
 
-``` syntax
+```xml
       <ProductVersion>
         <Major Minimum="2" />
       </ProductVersion>
@@ -443,7 +443,7 @@ Only the Minimum attribute is present. Maximum must be included in a range as we
 
 Only the Minor element is present. Major must be included as well.
 
-``` syntax
+```xml
       <ProductVersion>
         <Minor Minimum="0" Maximum="0" />
       </ProductVersion>
@@ -463,7 +463,7 @@ Including a FileVersion element for an application allows for more granular fine
 
 The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
 
-``` syntax
+```xml
       <Process>
         <Filename>MSACCESS.EXE</Filename>
         <Architecture>Win32</Architecture>

windows/configuration/ue-v/uev-manage-administrative-backup-and-restore.md

@@ -26,7 +26,7 @@ As an administrator of User Experience Virtualization (UE-V), you can restore ap
 
 To restore settings when a user adopts a new device, you can put a settings location template in **backup** or **roam (default)** profile using the Set-UevTemplateProfile PowerShell cmdlet. This lets computer settings sync to the new computer, in addition to user settings. Templates assigned to the backup profile are backed up for that device and configured on a per-device basis. To backup settings for a template, use the following cmdlet in Windows PowerShell:
 
-``` syntax
+```powershell
 Set-UevTemplateProfile -ID <TemplateID> -Profile <backup>
 ```
 
@@ -38,7 +38,7 @@ When replacing a user’s device, UE-V automatically restores settings if the us
 
 You can also use the Windows PowerShell cmdlet, Restore-UevBackup, to restore settings from a different device. To clone the settings packages for the new device, use the following cmdlet in Windows PowerShell:
 
-``` syntax
+```powershell
 Restore-UevBackup -ComputerName <Computer name>
 ```
 

windows/configuration/ue-v/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md

@@ -172,7 +172,7 @@ The UE-V Windows PowerShell features enable you to manage a group of settings te
 
 4.  Unregister all the previously registered versions of the templates by typing the following command.
 
-    ``` syntax
+    ```powershell
     Unregister-UevTemplate -All
     ```
 
@@ -180,7 +180,7 @@ The UE-V Windows PowerShell features enable you to manage a group of settings te
 
 5.  Register the updated templates by typing the following command.
 
-    ``` syntax
+    ```powershell
     Register-UevTemplate <path to template folder>\*.xml
     ```
 
@@ -192,7 +192,7 @@ By listing a Windows app in the Windows app list, you specify whether that app i
 
 To display the Package Family Name of installed Windows apps, at a Windows PowerShell command prompt, enter:
 
-``` syntax
+```powershell
 Get-AppxPackage | Sort-Object PackageFamilyName | Format-Table PackageFamilyName
 ```
 

windows/configuration/ue-v/uev-synchronizing-microsoft-office-with-uev.md

@@ -131,7 +131,7 @@ You can deploy UE-V settings location template with the following methods:
 
 -   **Registering template with PowerShell**. If you use Windows PowerShell to manage computers, run the following Windows PowerShell command as Administrator to register this settings location template:
 
-    ``` syntax
+    ```powershell
     Register-UevTemplate -Path <Path_to_Template>
     ```