From 9caf13ef87b113458872a06c702cf978b91899c9 Mon Sep 17 00:00:00 2001 From: Steven Hanna Date: Sat, 22 Apr 2017 13:39:57 -0400 Subject: [PATCH] spelling fixes without yaml (#3006) --- engine/userguide/networking/default_network/custom-docker0.md | 2 +- get-started/index.md | 4 ++-- get-started/part5.md | 2 +- get-started/part6.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/engine/userguide/networking/default_network/custom-docker0.md b/engine/userguide/networking/default_network/custom-docker0.md index c50a476f4a..6dcd57867a 100644 --- a/engine/userguide/networking/default_network/custom-docker0.md +++ b/engine/userguide/networking/default_network/custom-docker0.md @@ -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 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: ```bash diff --git a/get-started/index.md b/get-started/index.md index 18e8ea10e7..de3445d611 100644 --- a/get-started/index.md +++ b/get-started/index.md @@ -112,8 +112,8 @@ Consider this diagram comparing virtual machines to containers: ![Virtual machine stack example](https://www.docker.com/sites/default/files/VM%402x.png) 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 -an entangelment of OS settings, system-installed dependencies, OS security +This is resource intensive, and the resulting disk image and application state is +an entanglement of OS settings, system-installed dependencies, OS security patches, and other easy-to-lose, hard-to-replicate ephemera. ### Container diagram diff --git a/get-started/part5.md b/get-started/part5.md index f427257ddb..08b03e704d 100644 --- a/get-started/part5.md +++ b/get-started/part5.md @@ -30,7 +30,7 @@ machines running Docker, and deployed an application to it, with containers running in concert on multiple machines. 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 is capable of defining and coordinating the functionality of an entire application (though very complex applications may want to use multiple stacks). diff --git a/get-started/part6.md b/get-started/part6.md index 2d56e29237..48722c2dbe 100644 --- a/get-started/part6.md +++ b/get-started/part6.md @@ -162,7 +162,7 @@ Want to go deeper? Here are some resources we recommend: - [Samples](/samples/): Our samples include multiple examples of popular software 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. - [Admin Guide](/engine/admin/): Covers how to manage a Dockerized production environment.