From 5fdbbf37229a4ed4df8803cc75d416a9d8d53733 Mon Sep 17 00:00:00 2001 From: abuehrle Date: Tue, 2 Aug 2016 16:38:41 -0500 Subject: [PATCH] wording formatting --- site/weave-docker-api.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/site/weave-docker-api.md b/site/weave-docker-api.md index 4bf3972a..8619c5e8 100644 --- a/site/weave-docker-api.md +++ b/site/weave-docker-api.md @@ -9,7 +9,6 @@ network when they are started using the ordinary Docker or the [remote API](https://docs.docker.com/reference/api/docker_remote_api/), instead of `weave run`. - ###Attaching Containers to a Weave Network There are three ways to attach containers to a Weave network (which method to use is @@ -24,18 +23,17 @@ Docker containers are started with the --net flag, for example: **Where,** - * are the [docker run options](https://docs.docker.com/engine/reference/run/) + * `` are the [docker run options](https://docs.docker.com/engine/reference/run/) you give to your container on start Note that if a Docker container is started with the --net flag, then the Weave Docker API Proxy is automatically disabled and is not used to attach containers. See [Integrating Docker via the Network Plugin](plugin.md). - * Containers can also be attached to the Weave network by using `weave run` commands. This method also + * Containers can also be attached to the Weave network with `weave run` commands. This method also does not use the Weave Docker API Proxy. See [Launching Containers With Weave Run (without the Proxy)](/site/weave-docker-api/launching-without-proxy.md). - ###Setting Up The Weave Net Docker API Proxy The proxy sits between the Docker client (command line or API) and the