Update enable-exploit-protection.md

Author: denisebmsft

defender-endpoint/enable-exploit-protection.md

@@ -43,7 +43,7 @@ This section includes recommendations for you to be successful with deploying ex
 
 - Enable [full user mode dump](/windows/win32/wer/collecting-user-mode-dumps) collection
 
-- Check to see which applications are already compiled with "[Control Flow Guard](/windows/win32/secbp/control-flow-guard)" (CFG) which primarily focus on mitigating memory corruption vulnerabilities.  Use dumpbin tool to see if it's compiled w/ [CFG](/windows/win32/secbp/control-flow-guard). For these applications, you could skip enabling enforcement for DEP, ASRL, SEHOP, and ACG.
+- Check to see which applications are already compiled with "[Control Flow Guard](/windows/win32/secbp/control-flow-guard)" (CFG) which primarily focus on mitigating memory corruption vulnerabilities. Use dumpbin tool to see if it's compiled w/ [CFG](/windows/win32/secbp/control-flow-guard). For these applications, you could skip enabling enforcement for DEP, ASRL, SEHOP, and ACG.
 
 - Use safe deployment practices.
 
@@ -52,11 +52,11 @@ This section includes recommendations for you to be successful with deploying ex
 
 ### Safe deployment practices
 
-Safe deployment practices (SDP): Safe deployment processes and procedures define how to safely make and deploy changes to your workload.  Implementing SDP requires you to think about deployments through the lens of managing risk.  You can minimize the risk of end-user productivity outages in your deployments and limit the effects of problematic deployments on your users by implementing SDP.
+Safe deployment practices (SDP): Safe deployment processes and procedures define how to safely make and deploy changes to your workload. Implementing SDP requires you to think about deployments through the lens of managing risk. You can minimize the risk of end-user productivity outages in your deployments and limit the effects of problematic deployments on your users by implementing SDP.
 
-Start out with a small set (e.g. 10 to 50) of Windows devices and use that as your test environment to see which of the 21 mitigations, are incompatible with exploit protection.  Remove the mitigations that are not compatible with the application.  Reiterate with the applications that you are targeting. Once you feel that the policy is ready for production.
+Start out with a small set (for example, 10 to 50) of Windows devices and use that as your test environment to see which of the 21 mitigations, are incompatible with exploit protection. Remove the mitigations that aren't compatible with the application. Reiterate with the applications that you are targeting. Once you feel that the policy is ready for production.
 
-Start out by pushing first to User Acceptance Testing (UAT) usually comprised of the IT administrators, Security administrators and help desk personnel.  Then to 1%, 5%, 10%, 25%, 50%, 75%, and finally to 100% of your environment.
+Start out by pushing first to User Acceptance Testing (UAT) usually comprised of the IT administrators, Security administrators and help desk personnel. Then to 1%, 5%, 10%, 25%, 50%, 75%, and finally to 100% of your environment.
 
 ## Enabling exploit protection mitigations