1.2 additions for user-guide/

docs/user-guide/containers.md

@@ -18,9 +18,9 @@ we can use:
 
 Docker images have metadata associated with them that is used to store information about the image.
 The image author may use this to define defaults for the command and arguments to run a container
-when the user does not supply values. Docker calls the fields for commands and arguments
-`Entrypoint` and `Cmd` respectively. The full details for this feature are too complicated to
-describe here, mostly due to the fact that the Docker API allows users to specify both of these
+when the user does not supply values.  Docker calls the fields for commands and arguments
+`Entrypoint` and `Cmd` respectively.  The full details for this feature are too complicated to
+describe here, mostly due to the fact that the docker API allows users to specify both of these
 fields as either a string array or a string and there are subtle differences in how those cases are
 handled.  We encourage the curious to check out Docker's documentation for this feature.
 
@@ -50,7 +50,7 @@ Here are examples for these rules in table format
 
 By default, Docker containers are "unprivileged" and cannot, for example, run a Docker daemon inside a Docker container. We can have fine grain control over the capabilities using cap-add and cap-drop.More details [here](https://docs.docker.com/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration).
 
-The relationship between Docker's capabilities and [Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7)
+The relationship between Docker's capabilities and [Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)
 
 | Docker's capabilities | Linux capabilities |
 | ---- | ---- |