toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #12089 from nerdalert/doc-fix-netw-nerdalert

Browse Source 
Replaced level with layer for OSI model references
Upstream-commit: 4d4f201a4d453501dbe1fc049abad98c4933b237
Component: engine
This commit is contained in:
moxiegirl
2015-04-07 13:29:40 -07:00
parent ca7b99332a 4b42a60c0f
commit c9ca56fbcb
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/engine/docs/sources/article-img/ipv6_routed_network_example.gliffy
+1 -1
View File
File diff suppressed because one or more lines are too long
components/engine/docs/sources/article-img/ipv6_routed_network_example.svg
+1 -1
View File
File diff suppressed because one or more lines are too long
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 173 KiB

After

Width:  |  Height:  |  Size: 96 KiB

components/engine/docs/sources/articles/networking.md
+1 -1
View File
@@ -643,7 +643,7 @@ adapted to the individual environment.
#### Routed Network Environment
In a routed network environment you replace the level 2 switch with a level 3
In a routed network environment you replace the layer 2 switch with a layer 3
router. Now the hosts just have to know their default gateway (the router) and
the route to their own containers (managed by Docker). The router holds all
routing information about the Docker subnets. When you add or remove a host to