From 5c2aac47e91cb7f83e42540b682e8cac315435eb Mon Sep 17 00:00:00 2001
From: "[cmknox]" <[cmknox@gmail.com]>
Date: Wed, 3 Jul 2024 21:15:42 -0600
Subject: [PATCH] Fix link

---
 windows/deployment/do/delivery-optimization-configure.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/do/delivery-optimization-configure.md b/windows/deployment/do/delivery-optimization-configure.md
index 3b1fa6d16c..68dfb06058 100644
--- a/windows/deployment/do/delivery-optimization-configure.md
+++ b/windows/deployment/do/delivery-optimization-configure.md
@@ -113,7 +113,7 @@ There are several options for identifying your Group ID using the [DOGroupIDSour
 > [!NOTE]
 > If your peer group spans across NATs, the Teredo service will be used on port 3544.
 >
-> For Configuration Manager users, we recommend to leverage existing [MECM boundary groups](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management.md##delivery-optimization) to define the peer groups.
+> For Configuration Manager users, we recommend to leverage existing [boundary groups](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#delivery-optimization) to define the peer groups.
 
 ##### Restrict peer selection