@@ -375,7 +375,7 @@ networks.

 Within a user-defined bridge network, linking is not supported. You can

 expose and publish container ports on containers in this network. This is useful

-if you want make a portion of the `bridge` network available to an outside

+if you want to make a portion of the `bridge` network available to an outside

 network.

 ![Bridge network](images/network_access.png)

@@ -112,7 +112,7 @@ $ docker run -itd --name=container2 busybox

 498eaaaf328e1018042c04b2de04036fc04719a6e39a097a4f4866043a2c2152

 ```

-Then create a isolated, `bridge` network to test with.

+Then create an isolated, `bridge` network to test with.

 ```bash

 $ docker network create -d bridge isolated_nw

@@ -61,7 +61,7 @@ You can also use `docker inspect` with the container's name.

 Container names must be unique. That means you can only call one container

 `web`. If you want to re-use a container name you must delete the old container

-(with `docker rm`) before you can reuse the name with a new container. Go ahead and stop and them remove your `web` container.

+(with `docker rm`) before you can reuse the name with a new container. Go ahead and stop and remove your old `web` container.

     $ docker stop web

     web

@@ -73,7 +73,7 @@ Container names must be unique. That means you can only call one container

 Docker includes support for networking containers through the use of **network

 drivers**. By default, Docker provides two network drivers for you, the

-`bridge` and the `overlay` driver. You can also write a network driver plugin so

+`bridge` and the `overlay` drivers. You can also write a network driver plugin so

 that you can create your own drivers but that is an advanced task.

 Every installation of the Docker Engine automatically includes three default networks. You can list them: