Fix typos in two Network related pages (#19532)

* Fix typo in the Network page.

* Fix typos in the Bridge Network Driver page.

---------

Co-authored-by: Adeleke Akinade <adeleke.akinade@aat.org.uk>
This commit is contained in:
Adeleke Akinade 2024-02-29 10:41:07 +00:00 committed by GitHub
parent bc92dda6bf
commit 98b3164e57
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions

View File

@ -194,7 +194,7 @@ resolution.
Your container will have lines in `/etc/hosts` which define the hostname of the
container itself, as well as `localhost` and a few other common things. Custom
hosts, defined in `/etc/hosts` on the host machine, aren't inherited by
containers. To pass additional hosts into container, refer to [add entries to
containers. To pass additional hosts into a container, refer to [add entries to
container hosts file](../reference/cli/docker/container/run.md#add-host) in the
`docker run` reference documentation.

View File

@ -116,7 +116,7 @@ The following table describes the driver-specific options that you can pass to
Some of these options are also available as flags to the `dockerd` CLI, and you
can use them to configure the default `docker0` bridge when starting the Docker
daemon. The following tables shows which options have equivalent flags in the
daemon. The following table shows which options have equivalent flags in the
`dockerd` CLI.
| Option | Flag |
@ -168,7 +168,7 @@ $ docker network rm my-net
## Connect a container to a user-defined bridge
When you create a new container, you can specify one or more `--network` flags.
This example connects a Nginx container to the `my-net` network. It also
This example connects an Nginx container to the `my-net` network. It also
publishes port 80 in the container to port 8080 on the Docker host, so external
clients can access that port. Any other container connected to the `my-net`
network has access to all ports on the `my-nginx` container, and vice versa.