From a6db0f3995aed9eece795bb63ecee8adb387380b Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Tue, 16 Jan 2024 10:37:48 -0500
Subject: [PATCH] Update dynamic keyword object identifier in Windows Firewall
 documentation

---
 .../network-security/windows-firewall/dynamic-keywords.md     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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 792b396421..3bb0d451da 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
@@ -90,7 +90,7 @@ The following are requirements for the FQDN feature:
 
 This section provides some examples how to manage dynamic keywords using Windows PowerShell. A few important things to consider when using dynamic keywords are:
 
-- All dynamic keyword objects must have a unique GUID identifier to represent them
+- All dynamic keyword objects must have a unique identifier (GUID) to represent them
 - A firewall rule can use dynamic keywords instead of explicitly defining IP addresses for its conditions
 - A firewall rule can use both dynamic keywords and statically defined address ranges
 - A dynamic keyword object can be reused across multiple firewall rules
@@ -104,7 +104,7 @@ This section provides some examples how to manage dynamic keywords using Windows
 Here's an example script to allow an FQDN from PowerShell. Replace the `$fqdn` variable value with the FQDN you wish to block (line #1):
 
 ```PowerShell
-
+$fqdn = 'contoso.com'
 $id = '{' + (new-guid).ToString() + '}'
 New-NetFirewallDynamicKeywordAddress -id $id -Keyword $fqdn -AutoResolve $true
 New-NetFirewallRule -DisplayName "allow $fqdn" -Action Allow -Direction Outbound -RemoteDynamicKeywordAddresses $id