fix: editorial improvements

Signed-off-by: David Karlsson <david.karlsson@docker.com>
Co-authored-by: Aevesdocker <aevesdocker@users.noreply.github.com>

_data/toc.yaml

@@ -1353,7 +1353,7 @@ manuals:
     - sectiontitle: Network drivers
       section:
       - path: /network/drivers/
-        title: Drivers overview
+        title: Overview
       - path: /network/drivers/bridge/
         title: Bridge
       - path: /network/drivers/overlay/
@@ -1365,7 +1365,7 @@ manuals:
       - path: /network/drivers/macvlan/
         title: Macvlan
       - path: /network/drivers/none/
-        title: None
+        title: None (no networking)
     - path: /network/proxy/
       title: Configure Docker to use a proxy server
     - path: /config/daemon/ipv6/

engine/install/debian.md

@@ -19,11 +19,10 @@ To get started with Docker Engine on Debian, make sure you
 
 > **Note**
 >
-> If you use ufw to manage firewall settings, note that when you expose
+> If you use ufw to manage firewall settings, it's important to be aware that
-> container ports using Docker, those ports bypass any firewall rules that
+> when you expose container ports using Docker, these ports bypass any
-> you configure with ufw. See
+> firewall rules set up with ufw. For more information, refer to
-> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw)
+> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
-> for details.
 
 ### OS requirements
 

engine/install/raspbian.md

@@ -16,11 +16,10 @@ To get started with Docker Engine on Raspbian, make sure you
 
 > **Note**
 >
-> If you use ufw to manage firewall settings, note that when you expose
+> If you use ufw to manage firewall settings, it's important to be aware that
-> container ports using Docker, those ports bypass any firewall rules that
+> when you expose container ports using Docker, these ports bypass any
-> you configure with ufw. See
+> firewall rules set up with ufw. For more information, refer to
-> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw)
+> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
-> for details.
 
 ### OS requirements
 

engine/install/ubuntu.md

@@ -24,11 +24,10 @@ To get started with Docker Engine on Ubuntu, make sure you
 
 > **Note**
 >
-> If you use ufw to manage firewall settings, note that when you expose
+> If you use ufw to manage firewall settings, it's important to be aware that
-> container ports using Docker, those ports bypass any firewall rules that
+> when you expose container ports using Docker, these ports bypass any
-> you configure with ufw. See
+> firewall rules set up with ufw. For more information, refer to
-> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw)
+> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
-> for details.
 
 ### OS requirements
 

network/drivers/bridge.md

@@ -128,8 +128,8 @@ daemon. The following tables shows which options have equivalent flags in the
 | `com.docker.network.driver.mtu`                  | `--mtu`     |
 | `com.docker.network.container_iface_prefix`      | -           |
 
-The Docker daemon supports a `--bridge` flag, which you can use to define a
+The Docker daemon supports a `--bridge` flag, which you can use to define
-custom network bridge. You use this option if you want to run multiple daemon
+your own `docker0` bridge. Use this option if you want to run multiple daemon
 instances on the same host. For details, see
 [Run multiple daemons](../../engine/reference/commandline/dockerd.md#run-multiple-daemons).
 

network/drivers/index.md

@@ -42,12 +42,12 @@ exist by default, and provide core networking functionality:
 
 ### Network driver summary
 
-- The default bridge network is commonly used for running containers that don't
+- The default bridge network is good for running containers that don't require
-  require custom networking configurations, such as container-to-container
+  special networking capabilities.
-  connectivity.
+- User-defined bridge networks enable containers on the same Docker host to
-- User-defined bridge networks enable on the same Docker host to communicate
+  communicate with each other. A user-defined network typically defines an
-  with each other. A user-defined network typically defines an isolated network
+  isolated network for multiple containers belonging to a common project or
-  for multiple containers belonging to a common project or component.
+  component.
 - Host network shares the host's network with the container. When you use this
   driver, the container's network isn't isolated from the host.
 - Overlay networks are best when you need containers running on different

network/index.md

@@ -23,7 +23,7 @@ a gateway, a routing table, DNS services, and other networking details.
 That is, unless the container uses the `none` network driver.
 This page describes networking from the point of view of the container.
 
-This page describes the concepts around container networking.
+This page also describes the concepts around container networking.
 This page doesn't describe OS-specific details about how Docker networks work.
 For information about how Docker manipulates `iptables` rules on Linux,
 see [Packet filtering and firewalls](packet-filtering-firewalls.md).
@@ -116,7 +116,7 @@ of different factors:
 Under most circumstances, name resolution with multiple nameservers should work
 as follows:
 
-1. The container emits requests to **all** nameservers that you specify.
+1. The container emits requests to all nameservers that you specify.
 2. The container uses the first response returned by any of the nameservers.
    Even if the first response is `NXDOMAIN`, or similar.