From d63a21363eb03ff8a4e82d19efb9772cd0f054a8 Mon Sep 17 00:00:00 2001
From: Bryan Boreham <bjboreham@gmail.com>
Date: Fri, 8 Sep 2017 11:11:44 +0000
Subject: [PATCH 1/2] Add instructions on troubleshooting the V2 plugin

---
 site/install/plugin/plugin-v2.md |  1 +
 site/troubleshooting.md          | 22 ++++++++++++++++++++++
 2 files changed, 23 insertions(+)

diff --git a/site/install/plugin/plugin-v2.md b/site/install/plugin/plugin-v2.md
index be5ecb4d..19016a45 100644
--- a/site/install/plugin/plugin-v2.md
+++ b/site/install/plugin/plugin-v2.md
@@ -78,3 +78,4 @@ Or to start a container:
 
  * [Integrating Docker via the Network Plugin (Legacy)](/site/install/plugin/plugin.md)
  * [How the Weave Network Plugins Work](/site/install/plugin/plugin-how-it-works.md)
+ * [Troubleshooting the V2 plugin](/site/troubleshooting.md#v2plugin)
diff --git a/site/troubleshooting.md b/site/troubleshooting.md
index 03661925..8f6f6c9c 100644
--- a/site/troubleshooting.md
+++ b/site/troubleshooting.md
@@ -14,6 +14,7 @@ search_type: Documentation
    - [List attached containers](#list-attached-containers)
  * [Stopping Weave](#stop)
  * [Reboots](#reboots)
+ * [Troubleshooting the V2 plugin](#v2plugin)
  * [Snapshot Releases](#snapshots)
 
 ## <a name="diagnostics"></a>Basic Diagnostics
@@ -290,6 +291,27 @@ Proxy](/site/tasks/weave-docker-api/weave-docker-api.md) will re-attach any appl
 containers that it originally attached to the Weave network when they
 restart.
 
+## <a name="v2plugin"></a>Troubleshooting the V2 plugin
+
+If you have installed Weave Net via `docker plugin install`, then you
+will need to download the `weave` script to run `weave status`, `weave ps`
+or `weave report` as above.  Do this as described in the
+[install instructions](/site/install/installing-weave.md).
+
+Docker "v2" plugins run as containers, but at a lower level within the
+Docker environment, so you cannot view them with `docker ps`, `docker
+inspect`, etc.
+
+Do not run `weave launch`, `weave stop` or similar commands when using
+this plugin; use the `docker plugin` commands instead.  You can run
+`weave reset`, but only after disabling the plugin via `docker plugin disable`.
+
+Diagnostic logs from the plugin will go to the same place as the
+Docker daemon, which will depend on your Linux install. For example,
+if it uses `systemd`, then do this to view the Docker and plugin logs:
+
+    sudo journalctl -u docker
+
 ## <a name="snapshots"></a>Snapshot Releases
 
 Snapshot releases are published at times to provide previews of new

From a69546c9ee97f5847fb1c6aacd9258f436fa1461 Mon Sep 17 00:00:00 2001
From: Bryan Boreham <bjboreham@gmail.com>
Date: Tue, 26 Sep 2017 09:39:04 +0000
Subject: [PATCH 2/2] Reworded on review feedback

---
 site/troubleshooting.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/site/troubleshooting.md b/site/troubleshooting.md
index 8f6f6c9c..f47180ef 100644
--- a/site/troubleshooting.md
+++ b/site/troubleshooting.md
@@ -293,22 +293,22 @@ restart.
 
 ## <a name="v2plugin"></a>Troubleshooting the V2 plugin
 
-If you have installed Weave Net via `docker plugin install`, then you
-will need to download the `weave` script to run `weave status`, `weave ps`
-or `weave report` as above.  Do this as described in the
-[install instructions](/site/install/installing-weave.md).
+If Weave Net is installed via `docker plugin install`, download the
+`weave` script to run `weave status`, `weave ps` or `weave report` as
+above.  Install Weave Net by following the [install
+instructions](/site/install/installing-weave.md).
 
-Docker "v2" plugins run as containers, but at a lower level within the
-Docker environment, so you cannot view them with `docker ps`, `docker
-inspect`, etc.
+Docker "v2" plugins do run as containers, but at a lower level within
+the Docker environment.  Because of this, you cannot view them with
+`docker ps`, `docker inspect`, etc.
 
 Do not run `weave launch`, `weave stop` or similar commands when using
 this plugin; use the `docker plugin` commands instead.  You can run
 `weave reset`, but only after disabling the plugin via `docker plugin disable`.
 
-Diagnostic logs from the plugin will go to the same place as the
-Docker daemon, which will depend on your Linux install. For example,
-if it uses `systemd`, then do this to view the Docker and plugin logs:
+Diagnostic logs from the plugin go to the same place as the Docker
+daemon, which will depend on your Linux install. For example, if it
+uses `systemd`, then do this to view the Docker and plugin logs:
 
     sudo journalctl -u docker