diff --git a/windows/client-management/mdm/diagnose-provisioning-packages.md b/windows/client-management/mdm/diagnose-provisioning-packages.md
index c71e35a930..185b890101 100644
--- a/windows/client-management/mdm/diagnose-provisioning-packages.md
+++ b/windows/client-management/mdm/diagnose-provisioning-packages.md
@@ -17,7 +17,7 @@ ms.collection: highpri
 ## Unable to apply Power Settings
 When applying certain provisioning packages containing [power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11) they require elevated permissions which are not applied when applying PPKGs [after the initial setup](/windows/configuration/provisioning-packages/provisioning-apply-package#after-initial-setup). An error of STATUS_PRIVILEGE_NOT_HELD (HRESULT=0xc0000061) is given when applying these packages with the incorrect security context.
 
-Simply placing the PPKG into %WINDIR%/Provisioning/Packages and rebooting the machine will apply the packages with the [correct security context](../windows/win32/services/localsystem-account)) as stated in [Configure power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)
+Simply placing the PPKG into %WINDIR%/Provisioning/Packages and rebooting the machine will apply the packages with the [correct security context](../windows/win32/services/localsystem-account) as stated in [Configure power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)
 
 ## Unable to perform Bulk Enrollment in Azure AD
 See [allow enrollment into Azure AD for provisioning packages](https://techcommunity.microsoft.com/t5/intune-customer-success/bulk-join-a-windows-device-to-azure-ad-and-microsoft-endpoint/ba-p/2381400).
@@ -39,7 +39,7 @@ I think that now that the information is combined there is overlap and confusion
 Tooling has been included to surface these conditions in the event a certain target did not get applied.
 
 ## Diagnosing general failures in provisioning
-To help diagnose common problems, you can run the [mdmdiagnosticstool](../windows/client-management/diagnose-mdm-failures-in-windows-10) and capture multivariant condition values.
+To help diagnose common problems, you can run the [MdmDiagnosticsTool](../windows/client-management/diagnose-mdm-failures-in-windows-10) and capture multivariant condition values.
 
 ## Diagnosing multivariant problems
 When applying multivariant packages it may be difficult to see why a target was not applied. The [MdmDiagnosticsTool](../windows/client-management/diagnose-mdm-failures-in-windows-10) includes the multivariant condition values on the target system.