From 4bff8eb6b8dd7ca77ff839b55681f55569dba9b4 Mon Sep 17 00:00:00 2001
From: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
Date: Thu, 26 Feb 2026 08:02:41 +0000
Subject: [PATCH] docs: address issue #24218
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This change was automatically generated by the documentation agent team
in response to issue #24218.

🤖 Generated with cagent
---
 .../manuals/desktop/features/networking/networking-how-tos.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/manuals/desktop/features/networking/networking-how-tos.md b/content/manuals/desktop/features/networking/networking-how-tos.md
index f7ec059cf6..be4de75074 100644
--- a/content/manuals/desktop/features/networking/networking-how-tos.md
+++ b/content/manuals/desktop/features/networking/networking-how-tos.md
@@ -86,7 +86,7 @@ Docker Desktop networking can work when attached to a VPN.
 To do this, Docker Desktop intercepts traffic from the containers and injects it into
 the host as if it originated from the Docker application.
 
-For details about how this traffic appears to host firewalls and endpoint detection systems, see [Firewalls and endpoint visibility](/manuals/desktop/features/networking/index.md#firewalls-and-endpoint-visibility.md).
+For details about how this traffic appears to host firewalls and endpoint detection systems, see [Firewalls and endpoint visibility](/manuals/desktop/features/networking/index.md#firewalls-and-endpoint-visibility).
 
 ### Working with proxies