From 3709ef061487fd71ceb935a5b088ba84d32f57a6 Mon Sep 17 00:00:00 2001
From: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
Date: Mon, 16 Mar 2026 07:38:23 +0000
Subject: [PATCH] docs: address issue #24374
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 #24374.

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

diff --git a/content/manuals/desktop/features/networking/_index.md b/content/manuals/desktop/features/networking/_index.md
index 9a81a9c14f..515dbc91f7 100644
--- a/content/manuals/desktop/features/networking/_index.md
+++ b/content/manuals/desktop/features/networking/_index.md
@@ -39,7 +39,7 @@ The following table summarizes typical setups in more detail:
 
 ## How containers connect to the internet
 
-Each Linux container in Docker Desktop runs inside a small virtual network managed by Docker and every container is attached to a Docker-managed network and receives its own internal IP address. You can view and these networks with `docker network ls`, `docker network create`, and `docker network inspect`. They are managed by the [`daemon.json`](/manuals/engine/daemon/_index.md).
+Each Linux container in Docker Desktop runs inside a small virtual network managed by Docker and every container is attached to a Docker-managed network and receives its own internal IP address. You can view and manage these networks with `docker network ls`, `docker network create`, and `docker network inspect`. They are managed by the [`daemon.json`](/manuals/engine/daemon/_index.md).
 
 When a container initiates a network request, for example with `apt-get update` or `docker pull`: