kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Correct some typos for docs

Browse source 
Signed-off-by: Wen Cheng Ma <wenchma@cn.ibm.com>
This commit is contained in:
Wen Cheng Ma 2015-11-24 15:13:05 +08:00
parent ae1fadeb96
commit 4d66f18be0
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/userguide/networking/dockernetworks.md
View file

@ -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)

2
docs/userguide/networking/work-with-networks.md
View file

@ -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

4
docs/userguide/networkingcontainers.md
View file

@ -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: