From baf77a52d3588b6c0f31ab8442296d76f40e0ba8 Mon Sep 17 00:00:00 2001
From: Ryan Williams <103447364+Ryan-K-Williams@users.noreply.github.com>
Date: Mon, 6 Jan 2025 13:15:01 -0800
Subject: [PATCH] Update
 windows-autopatch-manage-driver-and-firmware-updates.md

As part of unification we changed the autopatch deferral period from 0-14 days to 0-30 days.
---
 .../windows-autopatch-manage-driver-and-firmware-updates.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md
index ddab13c440..e968491819 100644
--- a/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md
+++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md
@@ -68,7 +68,7 @@ For deployment rings set to **Automatic**, you can choose the deferral period fo
 
 The deferral period allows you to delay the installation of driver and firmware updates on the devices in the specified deployment ring in case you want to test the update on a smaller group of devices first or avoid potential disruptions during a busy period.  
 
-The deferral period can be set from 0 to 14 days, and it can be different for each deployment ring.  
+The deferral period can be set from 0 to 30 days, and it can be different for each deployment ring.  
 
 > [!NOTE]
 > The deferral period only applies to automatically approved driver and firmware updates. An admin must specify the date to start offering a driver with any manual approval.