From 1d7610c7ab36297e6ec2f29ee8ee0b794ac7d394 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Mon, 13 Feb 2023 13:37:42 -0800
Subject: [PATCH] Update windows-autopatch-windows-quality-update-overview.md

---
 .../windows-autopatch-windows-quality-update-overview.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 5b006d75d0..7ab913eb2c 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -55,7 +55,7 @@ Windows Autopatch configures these policies differently across deployment rings
 ## Release management
 
 > [!NOTE]
-> To access the Release Management blade, you must have the correct [role-based access control](../deploy/windows-autopatch-register-devices.md#built-in-roles-required-for-device-registration).
+> To access the Release management blade, you must have the correct [role-based access control](../deploy/windows-autopatch-register-devices.md#built-in-roles-required-for-device-registration).
 
 In the Release management blade, you can: