diff --git a/windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md b/windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md
index 3d46ca1532..6ab98f2f63 100644
--- a/windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md
+++ b/windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md
@@ -71,7 +71,7 @@ First, enable the mitigation using PowerShell, and then confirm that it has been
 
 Now that you know the mitigation has been enabled, you can test to see if it works and what the experience would be for an end user:
 
-1. Type **run** in the Start menu andp ress **Enter** to open the run dialog box.
+1. Type **run** in the Start menu and press **Enter** to open the run dialog box.
 
 2. Type **iexplore.exe** and press **Enter** or click **OK** to attempt to open Internet Explorer.
 
@@ -130,4 +130,4 @@ For further details on how audit mode works, and when you might want to use it,
 - [Comparison with Enhanced Mitigation Experience Toolkit](emet-exploit-protection-exploit-guard.md)
 - [Enable Exploit protection](enable-exploit-protection.md)
 - [Configure and audit Exploit protection mitigations](customize-exploit-protection.md)
-- [Import, export, and deploy Exploit protection configurations](import-export-exploit-protection-emet-xml.md)
\ No newline at end of file
+- [Import, export, and deploy Exploit protection configurations](import-export-exploit-protection-emet-xml.md)