Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
| ... | ... |
@@ -32,7 +32,7 @@ display your kernel version: |
| 32 | 32 |
$ uname -r |
| 33 | 33 |
3.10.0-229.el7.x86_64 |
| 34 | 34 |
|
| 35 |
-Finally, is it recommended that you fully update your system. Please keep in |
|
| 35 |
+Finally, it is recommended that you fully update your system. Please keep in |
|
| 36 | 36 |
mind that your system should be fully patched to fix any potential kernel bugs. |
| 37 | 37 |
Any reported kernel bugs may have already been fixed on the latest kernel |
| 38 | 38 |
packages. |
| ... | ... |
@@ -61,7 +61,7 @@ Four different options affect container domain name services. |
| 61 | 61 |
Using this option as you <code>run</code> a container gives the new |
| 62 | 62 |
container's <code>/etc/hosts</code> an extra entry named |
| 63 | 63 |
<code>ALIAS</code> that points to the IP address of the container |
| 64 |
- identified by <code>CONTAINER_NAME_or_ID<c/ode>. This lets processes |
|
| 64 |
+ identified by <code>CONTAINER_NAME_or_ID</code>. This lets processes |
|
| 65 | 65 |
inside the new container connect to the hostname <code>ALIAS</code> |
| 66 | 66 |
without having to know its IP. The <code>--link=</code> option is |
| 67 | 67 |
discussed in more detail below. Because Docker may assign a different IP |