From c4fa814ecd0671d2ea3bbe0c963eb9dfd3876c2a Mon Sep 17 00:00:00 2001 From: kamjar gerami Date: Mon, 28 Mar 2016 16:58:42 +0200 Subject: [PATCH] fixes-#21581-no--subnetwork-option-as-specified-in-docs-for-work-with-networks.md: fixed typo in docs Signed-off-by: kamjar gerami (cherry picked from commit a4d4243b9105d03b1e519729e8e8fd4b16084760) --- docs/userguide/networking/work-with-networks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide/networking/work-with-networks.md b/docs/userguide/networking/work-with-networks.md index 1a8586d941..6cd669484c 100644 --- a/docs/userguide/networking/work-with-networks.md +++ b/docs/userguide/networking/work-with-networks.md @@ -87,7 +87,7 @@ specify a single subnet. An `overlay` network supports multiple subnets. > in your infrastructure that is not managed by docker. Such overlaps can cause > connectivity issues or failures when containers are connected to that network. -In addition to the `--subnetwork` option, you also specify the `--gateway` `--ip-range` and `--aux-address` options. +In addition to the `--subnet` option, you also specify the `--gateway` `--ip-range` and `--aux-address` options. ```bash $ docker network create -d overlay