From 26b82c6f4bd767b5c7e88509cd85e408fe238eeb Mon Sep 17 00:00:00 2001 From: ayoshitake Date: Thu, 2 Jul 2015 23:05:14 -0700 Subject: [PATCH] Edit "Working with Containers" page for readability Signed-off-by: ayoshitake Upstream-commit: 0ed7fd46b6a02203bb6ddaf5cb004641e127da49 Component: engine --- components/engine/docs/userguide/usingdocker.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/components/engine/docs/userguide/usingdocker.md b/components/engine/docs/userguide/usingdocker.md index 32dff55d9a..cdf5f2543f 100644 --- a/components/engine/docs/userguide/usingdocker.md +++ b/components/engine/docs/userguide/usingdocker.md @@ -83,9 +83,8 @@ To see usage for a specific command, specify the command with the `--help` flag: So now we've learnt a bit more about the `docker` client let's move onto the important stuff: running more containers. So far none of the -containers we've run did anything particularly useful though. So let's -build on that experience by running an example web application in -Docker. +containers we've run did anything particularly useful, so let's +change that by running an example web application in Docker. For our web application we're going to run a Python Flask application. Let's start with a `docker run` command. @@ -303,7 +302,7 @@ And now our container is stopped and deleted. # Next steps Until now we've only used images that we've downloaded from -[Docker Hub](https://hub.docker.com) now let's get introduced to +[Docker Hub](https://hub.docker.com). Next, let's get introduced to building and sharing our own images. Go to [Working with Docker Images](/userguide/dockerimages).