diff --git a/site/installing.md b/site/installing.md
index 8106b21a9..5b28470c8 100644
--- a/site/installing.md
+++ b/site/installing.md
@@ -4,18 +4,19 @@ menu_order: 20
 ---
 
 
-Weave Scope consists of three parts: the probe, the app and the user interface.  Scope can be deployed in either a standalone configuration, where you run everything yourself, or by using Weave Cloud.  
+Weave Scope consists of three parts: the probe, the app and the user interface.  Scope can be deployed in either a standalone configuration, where you run everything yourself, or by using Weave Cloud.
 
 Weave Cloud is the recommended option if:
 
  * You are deploying to larger clusters.
  * You require secure remote access.
- * You wish to share access with your coworkers.
+ * You want to share access with your coworkers.
 
 The following topics are discussed:
 
  * [Installing Scope on Docker](#docker)
    * [Using Weave Cloud](#docker-weave-cloud)
+   * [Installing Scope on a Local Cluster Without Weave Net](#cluster-no-net)
    * [Weave Net and Scope](#net-scope)
    * [Using Docker Compose](#docker-compose)
    * [Using Docker Compose in Weave Cloud](#docker-compose-cloud)
@@ -27,7 +28,7 @@ The following topics are discussed:
 
 ##<a name="docker"></a>Installing Scope on Docker
 
-To install Scope onto your local Docker machine in standalone mode, run the following commands:
+To install Scope onto your machine with Docker installed in stand-alone mode, run the following commands:
 
     sudo curl -L git.io/scope -o /usr/local/bin/scope
     sudo chmod a+x /usr/local/bin/scope
@@ -43,7 +44,7 @@ Where,
 
  * `<VM name>` is the name you gave to your virtual machine with docker-machine.
 
-> **Note:** Scope allows anyone with access to the UI control over your containers: as such, the Scope app endpoint (port 4040) should not be made accessible on the Internet.  Additionally traffic between the app and the probe is currently insecure and should also not traverse the Internet.
+>>**Note:** Scope allows anyone with access to the user interface, control over your containers. As such, the Scope app endpoint (port 4040) should not be made accessible on the Internet.  Also traffic between the app and the probe is insecure and should not traverse the Internet. This means that you should either use the private / internal IP addresses of your nodes when setting it up, or route this traffic through Weave Net.  Put Scope behind a password, by using somthing like [Caddy](https://github.com/mholt/caddy) to protect the endpoint and make port 4040 available to localhost with Caddy proxying it. Or you can skip these steps, and just use Weave Cloud to manage the security for you.
 
 ###<a name="docker-weave-cloud"></a>Using Weave Cloud
 
@@ -59,9 +60,41 @@ Where,
 
 * `--service-token=<token>` is the token you obtained after you signed up for Weave Cloud.
 
-This script downloads and runs a recent Scope docker image from the Docker Hub. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it also doesn’t depend on Weave Net.
+This script downloads and runs a recent Scope Docker image from the Docker Hub. Scope needs to be installed onto every machine that you want to monitor. Once launched, Scope doesn’t require any other configuration and it does not depend on Weave Net.
+
+After Scope is launched, open your web browser to [https://cloud.weave.works](https://cloud.weave.works) and login. Click 'View Instance' in the top right-hand corner to see the Scope user interface.
+
+
+###<a name="cluster-no-net"></a>Installing Scope on a Local Cluster Without Weave Net
+
+This example assumes that you have a local cluster that is not using Weave Net, and which also has no special hostnames or DNS settings. Only the IP addresses assigned to it will be used to configure Scope. You will launch Scope using the IP addresses of all the nodes in the cluster. 
+
+Suppose you have the following cluster:
+
+ 192.168.100.16
+ 192.168.100.17
+ 192.168.100.18
+ 192.168.100.19
+ 192.168.100.20
+ 
+ In the steps that follow, you will manually peer each node with all of the other nodes during Scope launch. 
+ 
+**1. To begin run the following on each node:**
+
+     sudo curl -L git.io/scope -o /usr/local/bin/scope
+     sudo chmod a+x /usr/local/bin/scope
+
+ **2. Then on the first node run:**
+
+     scope launch 192.168.100.18 192.168.100.19 192.168.100.20
+
+ **3. And do the same for all of the other nodes in your cluster:**
+
+     scope launch 192.168.100.17 192.168.100.20 192.168.100.21
+     scope launch 192.168.100.17 192.168.100.18 192.168.100.21
+     scope launch 192.168.100.17 192.198.100.19 192.168.100.20
+
 
-After Scope has been launched, open your web browser to [https://cloud.weave.works](https://cloud.weave.works) and login. Click 'View Instance' in the top right-hand corner to see the Scope user interface.
 
 ###<a name="net-scope"></a> Weave Net and Scope