From 7526072c00a270c4c2eb8a4fd6e0f80ba34db687 Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Tue, 1 Apr 2025 14:31:19 -0700
Subject: [PATCH] add-comgmt-info

---
 windows/deployment/update/wufb-wsus.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md
index 9ae243af65..d2fdcadc77 100644
--- a/windows/deployment/update/wufb-wsus.md
+++ b/windows/deployment/update/wufb-wsus.md
@@ -39,13 +39,13 @@ We recommend using this policy on your transition from fully on-premises managed
 
 ## Default scan behavior
 
-To help you better understand the scan source policy, see the default scan behavior below and how we can change it:
+To help you better understand the scan source policy, see the following default scan behavior and how we can change it:
 
-- If no policies are configured: All of your updates will come from Windows Update.
+- If no policies are configured: All of your updates come from Windows Update.
 - If you configure only the WSUS server policy:
 
-  - On Windows 10: All of your updates will come from WSUS.
-  - On Windows 11: All of your updates will still come from WSUS unless you configure the specify scan source policy.
+  - On Windows 10: All of your updates come from WSUS.
+  - On Windows 11: All of your updates still come from WSUS unless you configure the specify scan source policy.
 
 - If you configure a WSUS server and deferral policies on Windows 10: All of your updates will come from Windows Update unless you specify the scan source policy or have disabled dual scan.
 - If you configure a WSUS server and the scan source policy: All of your updates will come from the source chosen in the scan source policy.