* Try to update the wording for the notes.
Signed-off-by: Charles Chan <charleswhchan@users.noreply.github.com>
| ... | ... |
@@ -133,8 +133,8 @@ This really long string is called a *container ID*. It uniquely |
| 133 | 133 |
identifies a container so we can work with it. |
| 134 | 134 |
|
| 135 | 135 |
> **Note:** |
| 136 |
-> The container ID is a bit long and unwieldy and a bit later |
|
| 137 |
-> on we'll see a shorter ID and some ways to name our containers to make |
|
| 136 |
+> The container ID is a bit long and unwieldy. A bit later, |
|
| 137 |
+> we'll see a shorter ID and ways to name our containers to make |
|
| 138 | 138 |
> working with them easier. |
| 139 | 139 |
|
| 140 | 140 |
We can use this container ID to see what's happening with our `hello world` daemon. |
| ... | ... |
@@ -157,8 +157,8 @@ is running, its status and an automatically assigned name, |
| 157 | 157 |
`insane_babbage`. |
| 158 | 158 |
|
| 159 | 159 |
> **Note:** |
| 160 |
-> Docker automatically names any containers you start, a |
|
| 161 |
-> little later on we'll see how you can specify your own names. |
|
| 160 |
+> Docker automatically generates names for any containers started. |
|
| 161 |
+> We'll see how to specify your own names a bit later. |
|
| 162 | 162 |
|
| 163 | 163 |
Okay, so we now know it's running. But is it doing what we asked it to do? To see this |
| 164 | 164 |
we're going to look inside the container using the `docker logs` |