cosmetic

site/proxy.md

@@ -129,10 +129,10 @@ paths which exist on the docker host.
 Because the proxy connects to the docker daemon at
 `unix:///var/run/docker.sock`, you must ensure that the daemon is
 listening there. To do this, you will need to pass the `-H
-unix:///var/run/docker.sock` option when starting the docker daemon, in
-addition to the `-H` options for configuring the TCP listener. See
-[the Docker
-documentation](https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket) for an example.
+unix:///var/run/docker.sock` option when starting the docker daemon,
+in addition to the `-H` options for configuring the TCP listener. See
+[the Docker documentation](https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket)
+for an example.
 
 With the proxy running over TLS, we can configure our regular docker
 client