From bc40f95d26ea47821c4c60c13047124afbf9bec0 Mon Sep 17 00:00:00 2001 From: illfated Date: Wed, 5 Feb 2020 21:05:37 +0100 Subject: [PATCH] BitLocker: typo in How to enable Network Unlock As pointed out in issue ticket (Typo), the word "local" is misspelled as "lcoal". This PR provides a simple typo correction. Thanks to Lexy2 for pointing out the typo. Proposed change: - Change the word "lcoal" to **local**. issue ticket reference or closure: Closes #5983 --- .../bitlocker/bitlocker-how-to-enable-network-unlock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md b/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md index 7cdd7f45b1..5ca3a201cf 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md +++ b/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md @@ -311,7 +311,7 @@ Troubleshooting Network Unlock issues begins by verifying the environment. Many - Group policy for Network Unlock is enabled and linked to the appropriate domains. - Verify group policy is reaching the clients properly. This can be done using the GPRESULT.exe or RSOP.msc utilities. - Verify the clients were rebooted after applying the policy. -- Verify the **Network (Certificate Based)** protector is listed on the client. This can be done using either manage-bde or Windows PowerShell cmdlets. For example the following command will list the key protectors currently configured on the C: drive of the lcoal computer: +- Verify the **Network (Certificate Based)** protector is listed on the client. This can be done using either manage-bde or Windows PowerShell cmdlets. For example the following command will list the key protectors currently configured on the C: drive of the local computer: ```powershell manage-bde -protectors -get C: