diff --git a/README.md b/README.md
index 1c430ec3..5ac4884d 100644
--- a/README.md
+++ b/README.md
@@ -64,15 +64,12 @@ First start weave on $HOST1:
 
     host1$ weave launch
 
-this runs the weave router, DNS and proxy, each in their own
-container. Next we configure our `DOCKER_HOST` environment variable to
-point to the proxy, so that containers launched via the docker command
-line are automatically attached to the weave network:
+Next we configure our environment so that containers launched via the
+docker command line are automatically attached to the weave network:
 
     host1$ eval $(weave proxy-env)
 
-Finally we run our application container; this happens via the proxy
-so it is automatically allocated an IP address and registered in DNS:
+Finally we run our application container:
 
     host1$ docker run --name a1 -ti ubuntu
 
@@ -100,11 +97,10 @@ available. Also, we can tell weave to connect to multiple peers by
 supplying multiple addresses, separated by spaces. And we can
 [add peers dynamically](http://docs.weave.works/weave/latest_release/features.html#dynamic-topologies).
 
-The router, DNS and proxy need to be started once per host. The
-relevant container images are pulled down on demand, but if you wish
-you can preload them by running `weave setup` - this is particularly
-useful for automated deployments, and ensures that there are no delays
-during later operations.
+Weave must be started once per host. The relevant container images are
+pulled down on demand, but if you wish you can preload them by running
+`weave setup` - this is particularly useful for automated deployments,
+and ensures that there are no delays during later operations.
 
 Now that we've got everything set up, let's see whether our containers
 can talk to each other...