diff --git a/windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md b/windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md
index c9851d72d1..676188aa12 100644
--- a/windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md
+++ b/windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md
@@ -70,6 +70,9 @@ When you have configured exploit protection to your desired state (including bot
 
 Change `filename` to any name or location of your choosing.
 
+Example command
+**Get-ProcessMitigation -RegistryConfigFilePath C:\ExploitConfigfile.xml**
+
 > [!IMPORTANT]
 > When you deploy the configuration using Group Policy, all machines that will use the configuration must be able to access the configuration file. Ensure you place the file in a shared location. 
 
@@ -91,6 +94,10 @@ After importing, the settings will be instantly applied and can be reviewed in t
 
 Change `filename` to the location and name of the exploit protection XML file.
 
+Example command
+**Set-ProcessMitigation -PolicyFilePath C:\ExploitConfigfile.xml**
+
+
 >[!IMPORTANT]
 >
 >Ensure you import a configuration file that is created specifically for exploit protection. You cannot directly import an EMET configuration file, you must convert it first.
@@ -151,6 +158,7 @@ You can use Group Policy to deploy the configuration you've created to multiple
     - C:\MitigationSettings\Config.XML
     -  \\\Server\Share\Config.xml
     -  https://localhost:8080/Config.xml
+    - C:\ExploitConfigfile.xml
 
 8. Click **OK** and [Deploy the updated GPO as you normally do](https://msdn.microsoft.com/library/ee663280(v=vs.85).aspx).