From dc1bb72d66217d37d70a0e4971b4d46e2930e4eb Mon Sep 17 00:00:00 2001 From: Iaan D'Souza-Wiltshire Date: Fri, 1 Dec 2017 18:45:10 +0000 Subject: [PATCH] Updated enable-controlled-folders-exploit-guard.md to remove strong language. --- .../enable-controlled-folders-exploit-guard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md b/windows/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md index 6912c28362..b0bc4e5eac 100644 --- a/windows/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md +++ b/windows/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md @@ -52,7 +52,7 @@ For further details on how audit mode works, and when you might want to use it, >[!NOTE] >The Controlled folder access feature will display the state in the Windows Defender Security Center app under **Virus & threat protection settings**. >If the feature is configured with Group Policy, PowerShell, or MDM CSPs, the state will change in the Windows Defender Security Center app after a restart of the device. ->If the feature is set to **Audit mode** with any of those tools, the Windows Defender Security Center app will show the state as **Off**, as protection offered by the feature will not work. +>If the feature is set to **Audit mode** with any of those tools, the Windows Defender Security Center app will show the state as **Off**. >See [Use audit mode to evaluate Windows Defender Exploit Guard features](audit-windows-defender-exploit-guard.md) for more details on how audit mode works.