chore: Replace "syntax" with code fence language

mdop/appv-v4/support-for-client-reporting-over-http.md

@@ -34,7 +34,7 @@ The client starts collecting data when it receives a “REPORTING=”TRUE””a
 
 The following schema gives specific details of the package and the application data that is sent to the server.
 
-``` syntax
+```xml
 <?xml version="1.0"?>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 

mdop/appv-v5/about-the-connection-group-virtual-environment.md

@@ -38,7 +38,7 @@ The connection group that is used is based on the order in which a package appea
 
 Consider the following example section:
 
-``` syntax
+```xml
 <appv:Packages><appv:PackagePackageId="A8731008-4523-4713-83A4-CD1363907160"VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"/><appv:PackagePackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"/><appv:PackagePackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"/></appv:Packages>
 ```
 

mdop/appv-v5/about-the-connection-group-virtual-environment51.md

@@ -38,7 +38,7 @@ The connection group that is used is based on the order in which a package appea
 
 Consider the following example section:
 
-``` syntax
+```xml
 <appv:Packages><appv:PackagePackageId="A8731008-4523-4713-83A4-CD1363907160"VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"/><appv:PackagePackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"/><appv:PackagePackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"/></appv:Packages>
 ```
 

mdop/appv-v5/application-publishing-and-client-interaction.md

@@ -811,7 +811,7 @@ This document focuses on App-V Full Infrastructure solutions. For specific infor
 
 The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md) or utilize the PowerShell:
 
-``` syntax
+```powershell
 get-command *appv*
 ```
 
@@ -1174,7 +1174,7 @@ The short cut is one of the basic elements of integration with the OS and is the
 
 From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following:
 
-``` syntax
+```xml
 <Extension Category="AppV.Shortcut">
           <Shortcut>
             <File>[{Common Desktop}]\Adobe Reader 9.lnk</File>
@@ -1194,7 +1194,7 @@ As mentioned previously, the App-V shortcuts are placed by default in the user
 
 The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below:
 
-``` syntax
+```xml
 <Extension Category="AppV.FileTypeAssociation">
           <FileTypeAssociation>
             <FileExtension MimeAssociation="true">
@@ -1323,7 +1323,7 @@ App-V supports specific software clients and application capabilities extension
 
 Example of software client registration of an App-V based mail client.
 
-``` syntax
+```xml
     <SoftwareClients Enabled="true">
       <ClientConfiguration EmailEnabled="true" />
       <Extensions>
@@ -1510,7 +1510,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **Manifest**
 
-``` syntax
+```xml
 <appv:Extension Category="AppV.Shortcut">
      <appv:Shortcut>
           <appv:File>[{Common Programs}]\7-Zip\7-Zip File Manager.lnk</appv:File>
@@ -1522,7 +1522,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **Deployment Configuration**
 
-``` syntax
+```xml
 <MachineConfiguration>
      <Subsystems>
           <Registry>
@@ -1537,7 +1537,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **User Configuration**
 
-``` syntax
+```xml
 <UserConfiguration>
      <Subsystems>
 <appv:ExtensionCategory="AppV.Shortcut">

mdop/appv-v5/application-publishing-and-client-interaction51.md

@@ -811,7 +811,7 @@ This document focuses on App-V Full Infrastructure solutions. For specific infor
 
 The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md) or utilize the PowerShell:
 
-``` syntax
+```powershell
 get-command *appv*
 ```
 
@@ -1174,7 +1174,7 @@ The short cut is one of the basic elements of integration with the OS and is the
 
 From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following:
 
-``` syntax
+```xml
 <Extension Category="AppV.Shortcut">
           <Shortcut>
             <File>[{Common Desktop}]\Adobe Reader 9.lnk</File>
@@ -1194,7 +1194,7 @@ As mentioned previously, the App-V shortcuts are placed by default in the user
 
 The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below:
 
-``` syntax
+```xml
 <Extension Category="AppV.FileTypeAssociation">
           <FileTypeAssociation>
             <FileExtension MimeAssociation="true">
@@ -1323,7 +1323,7 @@ App-V supports specific software clients and application capabilities extension
 
 Example of software client registration of an App-V based mail client.
 
-``` syntax
+```xml
     <SoftwareClients Enabled="true">
       <ClientConfiguration EmailEnabled="true" />
       <Extensions>
@@ -1510,7 +1510,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **Manifest**
 
-``` syntax
+```xml
 <appv:Extension Category="AppV.Shortcut">
      <appv:Shortcut>
           <appv:File>[{Common Programs}]\7-Zip\7-Zip File Manager.lnk</appv:File>
@@ -1522,7 +1522,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **Deployment Configuration**
 
-``` syntax
+```xml
 <MachineConfiguration>
      <Subsystems>
           <Registry>
@@ -1537,7 +1537,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio
 
 **User Configuration**
 
-``` syntax
+```xml
 <UserConfiguration>
      <Subsystems>
 <appv:ExtensionCategory="AppV.Shortcut">

mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md

@@ -227,7 +227,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
 
    2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file:
 
-      ``` syntax
+      ```xml
       <Configuration>
          <Add SourcePath= ”\\Server\Office2013” OfficeClientEdition="32" >
           <Product ID="O365ProPlusRetail ">
@@ -688,7 +688,7 @@ To exclude specific Office applications (for example, Access and InfoPath) when
 
 5.  Add the Office 2013 App-V Package with the new Deployment Configuration File.
 
-    ``` syntax
+    ```xml
     <Application Id="[{AppVPackageRoot)]\officefl5\INFOPATH.EXE" Enabled="true">
       <VisualElements>
         <Name>InfoPath Filler 2013</Name>

mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md

@@ -229,7 +229,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
 
     2.  With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file:
 
-        ``` syntax
+        ```xml
         <Configuration>
            <Add SourcePath= ”\\Server\Office2013” OfficeClientEdition="32" >
             <Product ID="O365ProPlusRetail ">
@@ -696,7 +696,7 @@ To exclude specific Office applications (for example, Access and InfoPath) when
 
 5.  Add the Office 2013 App-V Package with the new Deployment Configuration File.
 
-    ``` syntax
+    ```xml
     <Application Id="[{AppVPackageRoot)]\officefl5\INFOPATH.EXE" Enabled="true">
       <VisualElements>
         <Name>InfoPath Filler 2013</Name>

mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md

@@ -222,7 +222,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
 
    2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:
 
-      ``` syntax
+      ```xml
       <Configuration>
          <Add SourcePath= ”\\Server\Office2016” OfficeClientEdition="32" >
           <Product ID="O365ProPlusRetail ">
@@ -633,7 +633,7 @@ You may want to disable specific applications in your Office App-V package. For
 
 5.  Add the Office 2016 App-V Package with the new Deployment Configuration File.
 
-    ``` syntax
+    ```xml
     <Application Id="[{AppVPackageRoot}]\officel6\lync.exe" Enabled="true">
       <VisualElements>
         <Name>Lync 2016</Name>

mdop/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10.md

@@ -138,7 +138,7 @@ A file is provided that is named inv32.xml and contains remote connection inform
 
 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT:
 
-   ``` syntax
+   ```ini
    [LaunchApps]
    "%windir%\system32\netstart.exe -network -remount"
    "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage"

mdop/dart-v7/how-to-recover-remote-computers-using-the-dart-recovery-image-dart-7.md

@@ -131,7 +131,7 @@ A file is provided that is named inv32.xml and contains remote connection inform
 
 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT:
 
-   ``` syntax
+   ```ini
    [LaunchApps]
    "%windir%\system32\netstart.exe -network -remount"
    "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage"

mdop/dart-v8/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-8.md

@@ -138,7 +138,7 @@ A file is provided that is named inv32.xml and contains remote connection inform
 
 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT:
 
-   ``` syntax
+   ```ini
    [LaunchApps]
    "%windir%\system32\netstart.exe -network -remount"
    "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage"

mdop/mbam-v2/release-notes-for-mbam-20-mbam-2.md

@@ -38,7 +38,7 @@ If you are using the MBAM Stand-alone topology, and you upgrade the server infra
 
 WORKAROUND: After the upgrade, run the following script on the Compliance and Audit Database:
 
-``` syntax
+```sql
 -- =============================================
 -- Script Template
 -- =============================================

mdop/mbam-v25/mbam-25-security-considerations.md

@@ -134,7 +134,7 @@ You can configure the MBAM Recovery and Hardware Service with the name of this s
 
 -   Configure the group after the MBAM Recovery and Hardware Service has been installed by editing the web.config file in the <inetpub>\\Microsoft Bitlocker Management Solution\\Recovery and Hardware Service\\ folder.
 
-    ``` syntax
+    ```xml
     <add key="DataMigrationUsersGroupName" value="<groupName>|<empty>" />
     ```
 

windows/client-management/mdm/alljoynmanagement-csp.md

@@ -80,7 +80,7 @@ Boolean value indicating whether AllJoyn router service (AJRouter.dll) is enable
 
 Set adapter configuration
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
@@ -104,7 +104,7 @@ You should replace \_ALLJOYN\_DEVICE\_ID\_ with an actual device ID. Note that t
 
 Get PIN data
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
@@ -123,7 +123,7 @@ Get PIN data
 
 Get the firewall PrivateProfile
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
               <Get>

windows/client-management/mdm/applocker-ddf-file.md

@@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **AppLock
 
 Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN"
     "http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"

windows/client-management/mdm/applocker-xsd.md

@@ -17,7 +17,7 @@ ms.date: 06/26/2017
 
 Here's the XSD for the AppLocker CSP.
 
-``` syntax
+```xml
 <?xml version="1.0"?>  
 
 <xs:schema attributeFormDefault="unqualified"  

windows/client-management/mdm/appv-deploy-and-config.md

@@ -97,7 +97,7 @@ manager: dansimp
 
 <p>This example shows how to enable App-V on the device.</p>
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -117,7 +117,7 @@ manager: dansimp
 
 <p>This example shows how to allow package scripts to run during package operations (publish, run, and unpublish).  Allowing package scripts assists in package deployments (add and publish of App-V apps).</p>
 
-``` syntax
+```xml
 <Replace> 
 	<CmdID>$CmdID$</CmdID> 
 	<Item> 
@@ -141,7 +141,7 @@ manager: dansimp
 
 <p>This SyncML example shows how to publish a package globally on an MDM enrolled device for all device users.</p>
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -183,7 +183,7 @@ manager: dansimp
 
 <p>This SyncML example shows how to publish a package globally, with a policy that adds two shortcuts for the package, on an MDM enrolled device.</p>
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -277,7 +277,7 @@ manager: dansimp
 
 <p>This SyncML example shows how to publish a package for a specific MDM user.</p>
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -320,7 +320,7 @@ manager: dansimp
 > [!NOTE]
 > The user connection group has the user-only package as optional in this example, which implies users without the optional package can continue to launch the global package within the same connection group.
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -397,7 +397,7 @@ manager: dansimp
 
 <p>This SyncML example shows how to unpublish all global packages on the device by sending an empty package and connection group list in the SyncML.</p>
 
-``` syntax
+```xml
 <Replace>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -433,7 +433,7 @@ manager: dansimp
 
 <p>These SyncML examples return all global, and user-published packages on the device.</p>
 
-``` syntax
+```xml
 <Get>
 	<CmdID>$CmdID$</CmdID>
 	<Item>
@@ -444,7 +444,7 @@ manager: dansimp
 </Get>
 ```
 
-``` syntax
+```xml
 <Get>
 	<CmdID>$CmdID$</CmdID>
 	<Item>

windows/client-management/mdm/assignedaccess-csp.md

@@ -166,7 +166,7 @@ This MDM alert header is defined as follows:
 
 KioskModeApp Add
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Add>
@@ -188,7 +188,7 @@ KioskModeApp Add
 
 KioskModeApp Delete
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Delete>
@@ -206,7 +206,7 @@ KioskModeApp Delete
 
 KioskModeApp Get
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Get>
@@ -224,7 +224,7 @@ KioskModeApp Get
 
 KioskModeApp Replace
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Replace>
@@ -246,7 +246,7 @@ KioskModeApp Replace
 
 ## AssignedAccessConfiguration XSD
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 <xs:schema
     elementFormDefault="qualified"
@@ -390,7 +390,7 @@ KioskModeApp Replace
 
 ## Example AssignedAccessConfiguration XML
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8" ?>
 <AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config">
   <Profiles>
@@ -698,7 +698,7 @@ Example of the Delete command.
 
 ## StatusConfiguration XSD
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 <xs:schema
     elementFormDefault="qualified"
@@ -731,7 +731,7 @@ Example of the Delete command.
 
 StatusConfiguration Add OnWithAlerts
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
   <SyncBody>
     <Add>
@@ -760,7 +760,7 @@ StatusConfiguration Add OnWithAlerts
 
 
 StatusConfiguration Delete
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Delete>
@@ -778,7 +778,7 @@ StatusConfiguration Delete
 
 StatusConfiguration Get
 
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Get>
@@ -826,7 +826,7 @@ StatusConfiguration Replace On
 ## Status example
 
 Status Get
-``` syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
    <SyncBody>
        <Get>
@@ -844,7 +844,7 @@ Status Get
 
 ## ShellLauncherConfiguration XSD
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 <xs:schema
     elementFormDefault="qualified"
@@ -1195,7 +1195,7 @@ ShellLauncherConfiguration Get
 
 This example configures the following apps: Skype, Learning, Feedback Hub, and Calibration, for first line workers. Use this XML in a provisioning package using Windows Configuration Designer. For instructions, see [Configure HoloLens using a provisioning package](https://docs.microsoft.com/hololens/hololens-provisioning).
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="utf-8" ?>
 <!--
   This is a sample Assigned Access XML file. The Profile specifies which apps are allowed

windows/client-management/mdm/assignedaccess-ddf.md

@@ -24,7 +24,7 @@ You can download the DDF files from the links below:
 
 The XML below is for Windows 10, version 1803.
 
-``` syntax
+```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN"
   "http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"

windows/client-management/mdm/bitlocker-csp.md

@@ -66,7 +66,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -116,7 +116,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -178,7 +178,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px"> Sample value for this node to enable this policy and set the encryption methods is:</p>
 
-``` syntax
+```xml
  <enabled/><data id="EncryptionMethodWithXtsOsDropDown_Name" value="xx"/><data id="EncryptionMethodWithXtsFdvDropDown_Name" value="xx"/><data id="EncryptionMethodWithXtsRdvDropDown_Name" value="xx"/>
 ```
 
@@ -198,7 +198,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">  If you want to disable this policy use the following SyncML:</p> 
 
-``` syntax
+```xml
                           <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -269,7 +269,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/><data id="ConfigureNonTPMStartupKeyUsage_Name" value="xx"/><data id="ConfigureTPMStartupKeyUsageDropDown_Name" value="yy"/><data id="ConfigurePINUsageDropDown_Name" value="yy"/><data id="ConfigureTPMPINKeyUsageDropDown_Name" value="yy"/><data id="ConfigureTPMUsageDropDown_Name" value="yy"/>
 ```
 <p style="margin-left: 20px">Data id:</p>
@@ -296,7 +296,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -358,13 +358,13 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/><data id="MinPINLength" value="xx"/>
 ```
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -425,7 +425,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/><data id="PrebootRecoveryInfoDropDown_Name" value="xx"/><data id="RecoveryMessage_Input" value="yy"/><data id="RecoveryUrl_Input" value="zz"/>
 ```
 <p style="margin-left: 20px">The possible values for &#39;xx&#39; are:</p>
@@ -442,7 +442,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors.  If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                         <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -515,7 +515,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/><data id="OSAllowDRA_Name" value="xx"/><data id="OSRecoveryPasswordUsageDropDown_Name" value="yy"/><data id="OSRecoveryKeyUsageDropDown_Name" value="yy"/><data id="OSHideRecoveryPage_Name" value="xx"/><data id="OSActiveDirectoryBackup_Name" value="xx"/><data id="OSActiveDirectoryBackupDropDown_Name" value="zz"/><data id="OSRequireActiveDirectoryBackup_Name" value="xx"/>
 ```
 
@@ -542,7 +542,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -614,7 +614,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/><data id="FDVAllowDRA_Name" value="xx"/><data id="FDVRecoveryPasswordUsageDropDown_Name" value="yy"/><data id="FDVRecoveryKeyUsageDropDown_Name" value="yy"/><data id="FDVHideRecoveryPage_Name" value="xx"/><data id="FDVActiveDirectoryBackup_Name" value="xx"/><data id="FDVActiveDirectoryBackupDropDown_Name" value="zz"/><data id="FDVRequireActiveDirectoryBackup_Name" value="xx"/>
 ```
 
@@ -640,7 +640,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -696,13 +696,13 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
 <enabled/>
 ```
 
 <p style="margin-left: 20px">If you disable or do not configure this setting, all fixed data drives on the computer will be mounted with read and write access. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -764,7 +764,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Sample value for this node to enable this policy is:</p>
 
-``` syntax
+```xml
  <enabled/><data id="RDVCrossOrg" value="xx"/>
 ```
 
@@ -776,7 +776,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 
 <p style="margin-left: 20px">Disabling the policy will let the system choose the default behaviors. If you want to disable this policy use the following SyncML:</p>
 
-``` syntax
+```xml
                          <Replace>
                          <CmdID>$CmdID$</CmdID>
                            <Item>
@@ -827,7 +827,7 @@ The following diagram shows the BitLocker configuration service provider in tree
 -   0 – Disables the warning prompt. Starting in Windows 10, version 1803, the value 0 can only be set for Azure Active Directory joined devices.  Windows will attempt to silently enable BitLocker for value 0.
 -   1 (default) – Warning prompt allowed.
 
-``` syntax
+```xml
 <Replace>
     <CmdID>110</CmdID>
     <Item>
@@ -869,7 +869,7 @@ The expected values for this policy are:
 
 If you want to disable this policy use the following SyncML:
 
-``` syntax
+```xml
  <Replace>
  <CmdID>111</CmdID>
    <Item>
@@ -887,7 +887,7 @@ If you want to disable this policy use the following SyncML:
 
 The following example is provided to show proper format and should not be taken as a recommendation.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
     <SyncBody>
 

windows/security/identity-protection/credential-guard/additional-mitigations.md

@@ -334,7 +334,7 @@ write-host "There are no issuance policies which are not mapped to groups"
 
 Save the script file as set-IssuancePolicyToGroupLink.ps1.
 
-``` syntax
+```powershell
 #######################################
 ##     Parameters to be defined      ##
 ##     by the user                   ##