Merge pull request #8832 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)

Author: simonxjx

support/windows-server/certificates-and-public-key-infrastructure-pki/apps-forcibly-closed-tls-connection-errors.md

@@ -35,9 +35,9 @@ If you enabled [SChannel logging](/previous-versions/windows/it-pro/windows-serv
 
 ## Cause
 
-Windows 10, version 1511 and later versions of Windows, including Window Server 2016 or Windows 10, version 1607 that has updates released on Feb 25thor later updates installed, contains a leading zero update. Meanwhile, all Windows versions that released before that don't contain the leading zero updates.  
+Windows 10, version 1511 and later versions of Windows, including Window Server 2016 or Windows 10, version 1607 that has updates released on February 25, 2020, or later updates installed, contains a leading zero update. Meanwhile, all Windows versions that released before that don't contain the leading zero updates.  
 
-The TLS client and server need to calculate keys exactly the same way otherwise they get different results. TLS connections randomly fail if leading zeros are computed differently by the TLS client and TLS Servers.  
+The TLS client and server need to calculate keys exactly the same way, otherwise they get different results. TLS connections randomly fail if leading zeros are computed differently by the TLS client and TLS Servers.  
 
 When a [Diffie-Hellman key exchange](https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange) group has leading zeros, unpatched computers may incorrectly compute the mac by not accounting for the padded zeros. This issue is typically seen when interacting with non-Windows-based crypto implementations and can cause intermittent negotiation failures.