Mo-updates

windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers.md

@@ -19,11 +19,11 @@ Each CSP provides access to specific settings. For example, the [Wi-Fi CSP](/win
 
 CSPs receive configuration policies in the XML-based Synchronization Markup Language (SyncML) format, pushed from an MDM-compliant management server, such as Microsoft Intune. Traditional enterprise management systems, such as Microsoft Configuration Manager, can also target CSPs, by using a client-side Windows Management Instrumentation (WMI)-to-CSP Bridge.
 
-### Synchronization Markup Language (SyncML)
+## Synchronization Markup Language (SyncML)
 
 The Open Mobile Alliance Device Management (OMA-DM) protocol uses the XML-based SyncML for data exchange between compliant servers and clients. SyncML offers an open standard to use as an alternative to vendor-specific management solutions (such as WMI). The value for enterprises adopting industry standard management protocols is that it allows the management of a broader set of vendor devices using a single platform (such as Microsoft Intune). Device policies, including VPN connection profiles, are delivered to client devices formatted as in SyncML. The target CSP reads this information and applies the necessary configurations.
 
-### The WMI-to-CSP Bridge
+## The WMI-to-CSP Bridge
 
 The WMI-to-CSP Bridge is a component allowing configuration of Windows client CSPs using scripts and traditional enterprise management software, such as Configuration Manager using WMI. The bridge is responsible for reading WMI commands and through a component called the common device configurator pass them to a CSP for application on the device.
 
@@ -35,7 +35,7 @@ Generally, enterprises rely on Group Policy or MDM to configure and manage devic
 
 In addition, you may have unmanaged devices, or a large number of devices that you want to configure before enrolling them in management. You may also want to apply custom settings that aren't available through your MDM service. The [CSP documentation](/windows/client-management/mdm/configuration-service-provider-reference) can help you understand the settings that can be configured or queried. You can also learn about all of the available configuration settings.
 
-### CSPs in Windows Configuration Designer
+## CSPs in Windows Configuration Designer
 
 You can use Windows Configuration Designer to create [provisioning packages](provisioning-packages.md) to apply settings to devices during the out-of-box-experience (OOBE), and after the devices are set up. You can also use provisioning packages to configure a device's connectivity and enroll the device in MDM. Many of the runtime settings in Windows Configuration Designer are based on CSPs.
 
@@ -45,7 +45,7 @@ Many settings in Windows Configuration Designer display documentation for that s
 
 [Provisioning packages in Windows client](provisioning-packages.md) explains how to use the Windows Configuration Designer tool to create a runtime provisioning package.
 
-### CSPs in MDM
+## CSPs in MDM
 
 Most, if not all, CSPs are surfaced through your MDM service. If you see a CSP that provides a capability that you want to make use of and can't find that capability in your MDM service, contact your MDM provider for assistance. It might be named differently than you expected. You can see the CSPs supported by MDM in the [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference).
 

windows/configuration/provisioning-packages/provision-pcs-with-apps.md

@@ -27,7 +27,7 @@ When you add an app in a Windows Configuration Designer wizard, the appropriate
 - **Command line arguments**: Optionally, append more command arguments. The silent flag is appended for you. Example: PROPERTY=VALUE
 - **Continue installations after failure**: Optionally, specify if you want to continue installing more apps if this app fails to install
 - **Restart required**: Optionally, specify if you want to reboot after a successful install of this app
-- **Required win32 app dependencies**: Optionally, specify more files that are required for the installation of the app. For installers that have multiple file dependencies or have directory structures, [create a cab file of the assets](provisioning-script-to-install-app.md#cab-the-application-assets). The installation script should [include expansion of the .cab file](provisioning-script-to-install-app.md#cab-extract).
+- **Required win32 app dependencies**: Optionally, specify more files that are required for the installation of the app. For installers that have multiple file dependencies or have directory structures, [create a cab file of the assets](provisioning-script-to-install-app.md#cab-the-application-assets). The installation script should [include expansion of the .cab file](provisioning-script-to-install-app.md#extract-from-a-cab-example).
 
 > [!NOTE]
 > You can find more information about command-line options for Msiexec.exe [here](/windows/win32/msi/command-line-options).
@@ -38,7 +38,7 @@ When you add an app in a Windows Configuration Designer wizard, the appropriate
 - **Return Codes**: Specify the return codes for success and success with restart (0 and 3010 by default respectively) Any return code that isn't listed is interpreted as failure. The text boxes are space delimited.
 - **Continue installations after failure**: Optionally, specify if you want to continue installing more apps if this app fails to install
 - **Restart required**: Optionally, specify if you want to reboot after a successful install of this app
-- **Required win32 app dependencies**: Optionally, specify more files that are required for the installation of the app. For installers that have multiple file dependencies or have directory structures, [create a cab file of the assets](provisioning-script-to-install-app.md#cab-the-application-assets). The installation script should [include expansion of the .cab file](provisioning-script-to-install-app.md#cab-extract).
+- **Required win32 app dependencies**: Optionally, specify more files that are required for the installation of the app. For installers that have multiple file dependencies or have directory structures, [create a cab file of the assets](provisioning-script-to-install-app.md#cab-the-application-assets). The installation script should [include expansion of the .cab file](provisioning-script-to-install-app.md#extract-from-a-cab-example).
 
 ## Add a Windows desktop application using advanced editor
 
@@ -109,13 +109,11 @@ For details about the settings you can customize in provisioning packages, see [
     > [!TIP]
     > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store. Any package signed with that certificate can be applied silently.
 
-1. Select **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
-   Optionally, you can select **Browse** to change the default output location.
+1. Select **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location. Optionally, you can select **Browse** to change the default output location.
 
 1. Select **Next**.
 
-1. Select **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
-   If you need to cancel the build, select **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
+1. Select **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status. If you need to cancel the build, select **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
 
 1. If your build fails, an error message shows up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again. If your build is successful, the name of the provisioning package, output directory, and project directory is shown.
 

windows/configuration/provisioning-packages/provisioning-install-icd.md

@@ -65,5 +65,5 @@ Windows Configuration Designer can create provisioning packages for Windows clie
 > [!div class="nextstepaction"]
 > Learn more about creating a provisioning package:
 >
-> [Create a provisioning package (simple)](provision-pcs-for-initial-deployment.md)
+> [Create a provisioning package (desktop wizard)](provision-pcs-for-initial-deployment.md)
 > [Create a provisioning package (advanced)](provisioning-create-package.md)

windows/configuration/provisioning-packages/provisioning-script-to-install-app.md

@@ -105,8 +105,6 @@ PsExec.exe -accepteula -i -s cmd.exe /c 'powershell.exe my_powershell_script.ps1
 echo result: %ERRORLEVEL% >> %LOGFILE%
 ```
 
-<span id="cab-extract" />
-
 ### Extract from a .CAB example
 
 This example script shows expansion of a .cab from the provisioning commands script, and installation of the expanded setup.exe