@@ -97,7 +97,7 @@ disconnect` command.

 ## Specifying advanced options

-When you create a network, Engine creates a non-overlapping subnetwork for the network by default. This subnetwork is not a subdivision of an existing network. It is purely for ip-addressing purposes. You can override this default and specify subnetwork values directly using the the `--subnet` option. On a `bridge` network you can only create a single subnet:

+When you create a network, Engine creates a non-overlapping subnetwork for the network by default. This subnetwork is not a subdivision of an existing network. It is purely for ip-addressing purposes. You can override this default and specify subnetwork values directly using the `--subnet` option. On a `bridge` network you can only create a single subnet:

 ```bash

 docker network create -d --subnet=192.168.0.0/16

@@ -284,7 +284,7 @@ with `docker run --net none` which disables all incoming and outgoing

 networking. In cases like this, you would perform I/O through files or

 `STDIN` and `STDOUT` only.

-Publishing ports and linking to other containers only works with the the default (bridge). The linking feature is a legacy feature. You should always prefer using Docker network drivers over linking.

+Publishing ports and linking to other containers only works with the default (bridge). The linking feature is a legacy feature. You should always prefer using Docker network drivers over linking.

 Your container will use the same DNS servers as the host by default, but

 you can override this with `--dns`.

@@ -318,7 +318,7 @@ data. Then, you try and pull it.

         a9539b34a6ab: Pulling fs layer

         filesystem layer verification failed for digest sha256:aac0c133338db2b18ff054943cee3267fe50c75cdee969aed88b1992539ed042

-      You'll see the the pull did not complete because the trust system was

+      You'll see the pull did not complete because the trust system was

       unable to verify the image.

 ## More play in the sandbox

@@ -78,7 +78,7 @@ management that can assist your implementation.

 When you create a network, Engine creates a non-overlapping subnetwork for the

 network by default. You can override this default and specify a subnetwork

-directly using the the `--subnet` option. On a `bridge` network you can only

+directly using the `--subnet` option. On a `bridge` network you can only

 specify a single subnet. An `overlay` network supports multiple subnets.

 > **Note** : It is highly recommended to use the `--subnet` option while creating

@@ -241,7 +241,7 @@ should automatically load with the `btrfs` storage driver.

     The procedure for starting the Docker daemon may differ depending on the

     Linux distribution you are using.

-    You can force the the Docker daemon to start with the `btrfs` storage 

+    You can force the Docker daemon to start with the `btrfs` storage 

 driver by either passing the `--storage-driver=btrfs` flag to the `docker 

 daemon` at startup, or adding it to the `DOCKER_OPTS` line to the Docker config

  file.

@@ -87,7 +87,7 @@ images.

 If you look closely at the diagram you'll see that it's snapshots all the way 

 down. Each image layer is a snapshot of the layer below it. The lowest layer of

- each image is a snapshot of the the base device that exists in the pool. This 

+ each image is a snapshot of the base device that exists in the pool. This 

 base device is a `Device Mapper` artifact and not a Docker image layer.

 A container is a snapshot of the image it is created from. The diagram below 

@@ -81,7 +81,7 @@ Docker image comprising four layers.

     Status: Downloaded newer image for ubuntu:latest

 Each image layer has it's own directory under `/var/lib/docker/overlay/`. This 

-is where the the contents of each image layer are stored. 

+is where the contents of each image layer are stored. 

 The output of the command below shows the four directories that store the 

 contents of each image layer just pulled. However, as can be seen, the image 

@@ -96,7 +96,7 @@ disconnect` command.

 When you create a network, Engine creates a non-overlapping subnetwork for the

 network by default. This subnetwork is not a subdivision of an existing network.

 It is purely for ip-addressing purposes. You can override this default and

-specify subnetwork values directly using the the `--subnet` option. On a

+specify subnetwork values directly using the `--subnet` option. On a

 `bridge` network you can only create a single subnet:

 ```bash