docker/docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-11-05 00:14:17 +03:00
Code Activity

Merge pull request #377 from rillig/patch-1

Browse Source 
Fix spelling in Getting started, step two
This commit is contained in:
John Mulhausen
2016-10-28 17:12:26 -07:00
committed by GitHub
parent 14a611f87e d69c0184eb
commit a553ea8e8f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
engine/getstarted/step_two.md
View File

@@ -30,7 +30,7 @@ When you ran the command, Docker Engine:
* downloaded the image from the Docker Hub (more about the hub later)
* loaded the image into the container and "ran" it
Depending on how it was built, an image might run a simple, single command and then exit. This is what `Hello-World` did.
Depending on how it was built, an image might run a simple, single command and then exit. This is what `hello-world` did.
A Docker image, though, is capable of much more. An image can start software as complex as a database, wait for you (or someone else) to add data, store the data for later use, and then wait for the next person.