From d2191118552f1c2277907b6ce262990472d42b82 Mon Sep 17 00:00:00 2001 From: Zhang Wei Date: Thu, 17 Mar 2016 16:13:51 +0800 Subject: [PATCH] Fix typo Signed-off-by: Zhang Wei --- docs/reference/commandline/network_create.md | 2 +- docs/reference/run.md | 2 +- man/docker-network-create.1.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/commandline/network_create.md b/docs/reference/commandline/network_create.md index 6ae18e6e73..07df761efb 100644 --- a/docs/reference/commandline/network_create.md +++ b/docs/reference/commandline/network_create.md @@ -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 diff --git a/docs/reference/run.md b/docs/reference/run.md index 37ac49fb1b..d004300de5 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -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`. diff --git a/man/docker-network-create.1.md b/man/docker-network-create.1.md index 4d4cee3911..97505baf3b 100644 --- a/man/docker-network-create.1.md +++ b/man/docker-network-create.1.md @@ -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