document weave env --restore

leftover from #1327

site/proxy.md

@@ -60,6 +60,10 @@ command for this:
     host1$ docker ps
     ...
 
+The prior settings can be restored with
+
+    host1$ eval "$(weave env --restore)"
+
 Alternatively, the proxy host can be set on a per-command basis with
 
     host1$ docker $(weave config) ps
@@ -70,8 +74,9 @@ The proxy can be stopped independently with
 
 or in conjunction with the router and weaveDNS via `stop`.
 
-If you set your `DOCKER_HOST` to point at the proxy, remember to
-revert to the original setting.
+If you set your `DOCKER_HOST` to point at the proxy, you should revert
+to the original settings prior to stopping the proxy.
+
 
 ## <a name="usage"></a>Usage
 

site/troubleshooting.md

@@ -37,7 +37,13 @@ Another useful debugging technique is to attach standard packet
 capture and analysis tools, such as tcpdump and wireshark, to the
 `weave` network bridge on the host.
 
-To stop weave, run
+To stop weave, if you have configured your environment to use the
+Weave Docker API Proxy, e.g. by running `eval $(weave env)` in your
+shell, you must first restore the environment with
+
+    eval $(weave env --restore)
+
+Then run
 
     weave stop