mirror of https://github.com/docker/docs.git
spelling fixes without yaml (#3006)
This commit is contained in:
parent
958fb121b0
commit
9caf13ef87
|
@ -34,7 +34,7 @@ Docker configures `docker0` with an IP address, netmask and IP allocation range.
|
||||||
|
|
||||||
Once you have one or more containers up and running, you can confirm that Docker has properly connected
|
Once you have one or more containers up and running, you can confirm that Docker has properly connected
|
||||||
them to the `docker0` bridge by running the `brctl` command on the host machine and looking at the
|
them to the `docker0` bridge by running the `brctl` command on the host machine and looking at the
|
||||||
`interfaces` column of the output. Thhis example shows a `docker0` bridge with two containers
|
`interfaces` column of the output. This example shows a `docker0` bridge with two containers
|
||||||
connected:
|
connected:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|
|
@ -112,8 +112,8 @@ Consider this diagram comparing virtual machines to containers:
|
||||||

|

|
||||||
|
|
||||||
Virtual machines run guest operating systems -- note the OS layer in each box.
|
Virtual machines run guest operating systems -- note the OS layer in each box.
|
||||||
This is resource intensive, and the resulting disk image and appication state is
|
This is resource intensive, and the resulting disk image and application state is
|
||||||
an entangelment of OS settings, system-installed dependencies, OS security
|
an entanglement of OS settings, system-installed dependencies, OS security
|
||||||
patches, and other easy-to-lose, hard-to-replicate ephemera.
|
patches, and other easy-to-lose, hard-to-replicate ephemera.
|
||||||
|
|
||||||
### Container diagram
|
### Container diagram
|
||||||
|
|
|
@ -30,7 +30,7 @@ machines running Docker, and deployed an application to it, with containers
|
||||||
running in concert on multiple machines.
|
running in concert on multiple machines.
|
||||||
|
|
||||||
Here in part 5, you'll reach the top of the hierarchy of distributed
|
Here in part 5, you'll reach the top of the hierarchy of distributed
|
||||||
applications: the **stack**. A stack is a group of interelated services that
|
applications: the **stack**. A stack is a group of interrelated services that
|
||||||
share dependencies, and can be orchestrated and scaled together. A single stack
|
share dependencies, and can be orchestrated and scaled together. A single stack
|
||||||
is capable of defining and coordinating the functionality of an entire
|
is capable of defining and coordinating the functionality of an entire
|
||||||
application (though very complex applications may want to use multiple stacks).
|
application (though very complex applications may want to use multiple stacks).
|
||||||
|
|
|
@ -162,7 +162,7 @@ Want to go deeper? Here are some resources we recommend:
|
||||||
|
|
||||||
- [Samples](/samples/): Our samples include multiple examples of popular software
|
- [Samples](/samples/): Our samples include multiple examples of popular software
|
||||||
running in containers, and some good labs that teach best practices.
|
running in containers, and some good labs that teach best practices.
|
||||||
- [User Guide](/engine/userguide/): The user guide has serveral examples that
|
- [User Guide](/engine/userguide/): The user guide has several examples that
|
||||||
explain networking and storage in greater depth than was covered here.
|
explain networking and storage in greater depth than was covered here.
|
||||||
- [Admin Guide](/engine/admin/): Covers how to manage a Dockerized production
|
- [Admin Guide](/engine/admin/): Covers how to manage a Dockerized production
|
||||||
environment.
|
environment.
|
||||||
|
|
Loading…
Reference in New Issue