Skip to content

Commit 481e8bc

Browse files
docs: address issue #24374 (#24375)
## Summary Fixed incomplete sentence in Docker Desktop networking documentation. ## Changes - Corrected grammatically incorrect sentence in "How containers connect to the internet" section by changing "view and these networks" to "view and manage these networks" Fixes #24374 --- 🤖 Generated with [Docker Agent](https://github.com/docker/docker-agent) Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
1 parent 9b3869f commit 481e8bc

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • content/manuals/desktop/features/networking

content/manuals/desktop/features/networking/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The following table summarizes typical setups in more detail:
3939

4040
## How containers connect to the internet
4141

42-
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).
42+
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).
4343

4444
When a container initiates a network request, for example with `apt-get update` or `docker pull`:
4545

0 commit comments

Comments
 (0)