Update evaluate-exploit-protection.md

Author: denisebmsft

defender-endpoint/evaluate-exploit-protection.md

@@ -57,12 +57,12 @@ Services
 
 ## Application compatibility list
 
-The following table lists specific products that have compatibility issues with the mitigations that are included in exploit protection. You must disable specific incompatible mitigations if you want to protect the product by using exploit protection. Be aware that this list takes into consideration the default settings for the latest versions of the product.  Compatibility issues can introduced when you apply certain add-ins or additional components to the standard software.
+The following table lists specific products that have compatibility issues with the mitigations that are included in exploit protection. You must disable specific incompatible mitigations if you want to protect the product by using exploit protection. Be aware that this list takes into consideration the default settings for the latest versions of the product.  Compatibility issues can introduced when you apply certain add-ins or other components to the standard software.
 
 | Product | Exploit protection mitigation |
 | -------- | -------- |
 | .NET 2.0/3.5   | EAF/IAF   |
-| 7-Zip Console/GUI/File Manager   | EAF   |
+| 7-Zip Console/GUI/File Manager   | EAF  |
 | AMD 62xx processors  | EAF   |
 | Avecto (Beyond Trust) Power Broker   | EAF, EAF+, Stack Pivot   |
 | Certain AMD (ATI) video drivers   | System ASLR=AlwaysOn   |
@@ -80,7 +80,7 @@ The following table lists specific products that have compatibility issues with
 | SolarWinds Syslogd Manager   | EAF  |
 | Windows Media Player   | MandatoryASLR, EAF|
 
-ǂ EMET mitigations might be incompatible with Oracle Java when they are run by using settings that reserve a large chunk of memory for the virtual machine (that is, by using the -Xms option).
+ǂ EMET mitigations might be incompatible with Oracle Java when they're run by using settings that reserve a large chunk of memory for the virtual machine (that is, by using the -Xms option).
 
 ## Enable exploit protection for testing
 
@@ -101,7 +101,7 @@ You can set mitigations in a testing mode for specific programs by using the Win
       - Use **Add by program name** to have the mitigation applied to any running process with that name. Specify a file with an extension. You can enter a full path to limit the mitigation to only the app with that name in that location.
       - Use **Choose exact file path** to use a standard Windows Explorer file picker window to find and select the file you want.
 
-4. After selecting the app, you'll see a list of all the mitigations that can be applied. Choosing **Audit** will apply the mitigation in test mode only. You'll be notified if you need to restart the process, app, or Windows.
+4. After selecting the app, you'll see a list of all the mitigations that can be applied. Choosing **Audit** applies the mitigation in test mode only. You are notified if you need to restart the process, app, or Windows.
 
 5. Repeat this procedure for all the apps and mitigations you want to configure. Select **Apply** when you're done setting up your configuration.
 
@@ -144,7 +144,7 @@ You can disable **audit mode** by replacing `-Enable` with `-Disable`.
 
 ## Review exploit protection audit events
 
-To review which apps would have been blocked, open Event Viewer and filter for the following events in the Security-Mitigations log.<br/><br/>
+To review which apps would be blocked, open Event Viewer and filter for the following events in the Security-Mitigations log.
 
 |Feature|Provider/source|Event ID|Description|
 |---|---|--|---|