From 681e5e099c04320d7af029d5a653871c33c65436 Mon Sep 17 00:00:00 2001
From: brbrahm <43386070+brbrahm@users.noreply.github.com>
Date: Mon, 29 Jul 2019 10:31:22 -0700
Subject: [PATCH] Minor update to properly reflect supported macros

---
 .../create-path-based-rules.md                            | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
index 105f6a46bb..babbce2e0b 100644
--- a/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
+++ b/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules.md
@@ -52,10 +52,10 @@ Beginning with Windows 10 version 1903, Windows Defender Application Control (WD
   - Suffix (ex. C:\foo\\*) OR Prefix (ex. *\foo\bar.exe)
     - One or the other, not both at the same time
     - Does not support wildcard in the middle (ex. C:\\*\foo.exe)
-  - Examples:
-    - %WINDIR%\\...
-    - %SYSTEM32%\\...
-    - %OSDRIVE%\\...
+- Supported Macros:
+  - %WINDIR%\\...
+  - %SYSTEM32%\\...
+  - %OSDRIVE%\\...
 
 - Disable default FilePath rule protection of enforcing user-writeability. For example, to add “Disabled:Runtime FilePath Rule Protection” to the policy: