Reword a sentence bringing confusion about docker links
| ... | ... |
@@ -159,8 +159,8 @@ Next, inspect your linked containers with `docker inspect`: |
| 159 | 159 |
You can see that the `web` container is now linked to the `db` container |
| 160 | 160 |
`web/db`. Which allows it to access information about the `db` container. |
| 161 | 161 |
|
| 162 |
-So what does linking the containers actually do? You've learned that a link creates a |
|
| 163 |
-source container that can provide information about itself to a recipient container. In |
|
| 162 |
+So what does linking the containers actually do? You've learned that a link allows a |
|
| 163 |
+source container to provide information about itself to a recipient container. In |
|
| 164 | 164 |
our example, the recipient, `web`, can access information about the source `db`. To do |
| 165 | 165 |
this, Docker creates a secure tunnel between the containers that doesn't need to |
| 166 | 166 |
expose any ports externally on the container; you'll note when we started the |