diff --git a/windows/security/operating-system-security/network-security/windows-firewall/dynamic-keywords.md b/windows/security/operating-system-security/network-security/windows-firewall/dynamic-keywords.md
index 1a04f91043..275f7adfa9 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/dynamic-keywords.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/dynamic-keywords.md
@@ -75,7 +75,6 @@ The following are requirements for the FQDN feature:
   - [Chrome][HTTP-1]
   - [Firefox][HTTP-2]
 - The device's default DNS resolution settings apply. This feature doesn't provide DNS security or functionality changes
-  - For Microsoft Edge version 109 and later, configure the browser to use the default system DNS through [this policy][EDGE-2]. For more information, see [Configure Microsoft Edge policy settings on Windows devices][EDGE-3]
     > [!TIP]
     > You can also download the ADMX file from there, follow the directions, and configure it via gpedit.msc for local testing.
 
@@ -129,7 +128,7 @@ Get-NetFirewallDynamicKeywordAddress -AllAutoResolve
 
 ### Hydrate FQDN rules
 
-The following sample scripts read the current Windows Firewall configuration, extract FQDN-based rules, and perform DNS resolution on each domain. The result is that the IP addresses for those rules get populated.
+The following sample scripts read the current Windows Firewall configuration, extract FQDN-based rules, and perform DNS resolution on each domain. The result is that the IP addresses for those rules get "prehydrated."
 
 ```PowerShell
 Get-NetFirewallDynamicKeywordAddress -AllAutoResolve |`