Merged PR 11756: Fixed formatting

Fixed formatting

windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md

@@ -54,9 +54,7 @@ You can use the Windows Security app or Group Policy to add and remove additiona
 3. Under the **Controlled folder access** section, click **Protected folders**
 
 4. Click **Add a protected folder** and follow the prompts to add apps.
-
-   ![Screenshot of the Virus and threat protection settings button](images/cfa-prot-folders.png)
-
+ 
 ### Use Group Policy to protect additional folders
 
 1.  On your Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.

windows/security/threat-protection/windows-defender-exploit-guard/customize-exploit-protection.md

@@ -11,7 +11,7 @@ ms.pagetype: security
 ms.localizationpriority: medium
 author: andreabichsel
 ms.author: v-anbic
-ms.date: 08/08/2018
+ms.date: 10/02/2018
 ---
 
 # Customize exploit protection
@@ -39,8 +39,6 @@ You can set each of the mitigations to on, off, or to their default value. Some
 
 Default values are always specified in brackets at the **Use default** option for each mitigation. In the following example, the default for Data Execution Prevention is "On". 
 
-![Screenshot showing the drop down menu for DEP which shows the default for DEP as On](images/ep-default.png)
-
 The **Use default** configuration for each of the mitigation settings indicates our recommendation for a base level of protection for everyday usage for home users. Enterprise deployments should consider the protection required for their individual needs and may need to modify configuration away from the defaults.
 
 For the associated PowerShell cmdlets for each mitigation, see the [PowerShell reference table](#cmdlets-table) at the bottom of this topic.
@@ -116,9 +114,7 @@ Validate stack integrity (StackPivot) | Ensures that the stack has not been redi
     >[!NOTE]
     >You may see a User Account Control window when changing some settings. Enter administrator credentials to apply the setting.
 
-    Changing some settings may required a restart, which will be indicated in red text underneath the setting.
-
-    ![Screenshot showing the DEP drop down menu where you can select On, Off, or Default](images/wdsc-exp-prot-sys-settings.png)
+    Changing some settings may required a restart, which will be indicated in red text underneath the setting.	  
 
 4. Repeat this for all the system-level mitigations you want to configure.
 
@@ -138,15 +134,11 @@ Exporting the configuration as an XML file allows you to copy the configuration
     2. If the app is not listed, at the top of the list click **Add program to customize** and then choose how you want to add the app:
         - Use **Add by program name** to have the mitigation applied to any running process with that name. You must 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.
-
-        ![Screenshot showing the add file or folder button](images/wdsc-exp-prot-app-settings.png)
-
+		        
 4. After selecting the app, you'll see a list of all the mitigations that can be applied. To enable the mitigation, click the check box and then change the slider to **On**. Select any additional options. Choosing **Audit** will apply the mitigation in audit mode only. You will be notified if you need to restart the process or app, or if you need to restart Windows.
 
 5. Repeat this for all the apps and mitigations you want to configure. Click **Apply** when you're done setting up your configuration.
-
-    ![Screenshot showing some of the options available for an added program](images/wdsc-exp-prot-app-settings-options.png)
-
+    
 You can now [export these settings as an XML file](import-export-exploit-protection-emet-xml.md) or return to configure system-level mitigations. 
 
 Exporting the configuration as an XML file allows you to copy the configuration from one machine onto other machines.