From a6b2519c6d5179a5df465296104640fec75d77af Mon Sep 17 00:00:00 2001
From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com>
Date: Sun, 5 Apr 2020 15:12:43 +0500
Subject: [PATCH] Update
 windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md

Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../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 9749ee1793..a7a7e7fce7 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
@@ -82,7 +82,7 @@ The server side configuration to enable Network Unlock also requires provisionin
 2.  The client computer uses its DHCP driver in the UEFI to obtain a valid IPv4 IP address.
 3.  The client computer broadcasts a vendor-specific DHCP request that contains: 
     1.  A Network Key (a 256-bit intermediate key) encrypted using the 2048-bit RSA Public Key of the Network Unlock certificate from the WDS server.
-    2.  AES-256 session key for the reply.
+    2.  An AES-256 session key for the reply.
 4.  The Network Unlock provider on the WDS server recognizes the vendor-specific request.
 5.  The provider decrypts it with the WDS server’s BitLocker Network Unlock certificate RSA private key.
 6.  The WDS provider then returns the network key encrypted with the session key using its own vendor-specific DHCP reply to the client computer. This forms an intermediate key.