What should work before proceeding
diff --git a/xos/configurations/cord-pod/README.md b/xos/configurations/cord-pod/README.md
index 871bd30..c300416 100644
--- a/xos/configurations/cord-pod/README.md
+++ b/xos/configurations/cord-pod/README.md
@@ -73,15 +73,15 @@
 ubuntu@xos:~$ cd xos/xos/configurations/cord-pod
 ```
 
-Next, check that the following files exist in this directory:
+Next, check that the following files exist in this directory 
+(they will have been put there for you by the cluster installation scripts):
 
  * *admin-openrc.sh*: Admin credentials for your OpenStack cloud
  * *id_rsa[.pub]*: A keypair that will be used by the various services
  * *node_key*: A private key that allows root login to the compute nodes
 
-They will have been put there for you by the cluster installation scripts.
-
-XOS can then be brought up for CORD by running a few `make` commands:
+XOS can then be brought up for CORD by running a few `make` commands.
+First, run:
 
 ```
 ubuntu@xos:~/xos/xos/configurations/cord-pod$ make
@@ -103,10 +103,10 @@
 and pushing it to ONOS.  **If you are not setting up the single-node development POD**, you will 
 need to modify the generated configuration via the XOS GUI. (The defaults
 should be OK for the single-node POD.)  For more information
-about how to configure VTN, see [this page on the ONOS Wiki](https://wiki.onosproject.org/display/ONOS/CORD+VTN),
+about how to configure VTN, see [the CORD VTN page on the ONOS Wiki](https://wiki.onosproject.org/display/ONOS/CORD+VTN),
 under the **ONOS Settings** heading.   
 
-* To see the generated configuration, go to http://xos/admin/onos/onosapp/, select
+* To see the generated configuration, go to *http://xos/admin/onos/onosapp/*, select
 *VTN_ONOS_app*, then the *Attributes* tab, and look for the
 `rest_onos/v1/network/configuration/` attribute.  
 
@@ -116,12 +116,29 @@
 and then select *Save*.
 
 * To change `bridgeId`, `dataPlaneIntf`, or `dataPlaneIp` for a particular compute node, go to
-http://xos/admin/core/node/, select a node, then select the *Tags* tab.  Modify the appropriate tag
+*http://xos/admin/core/node/*, select a node, then select the *Tags* tab.  Modify the appropriate tag
 and then select *Save*.
 
 * After modifying the above fields, delete the `rest_onos/v1/network/configuration/` attribute
 in the *ONOS_VTN_app* and select *Save*.  The attribute will be regenerated using the new information.
 
+* Alternatively, if you want to load your own VTN configuration manually, you can delete the 
+`autogenerate` attribute from the *ONOS_VTN_app*, paste your configuration in the 
+`rest_onos/v1/network/configuration/` attribute, and select *Save*.
+
+Before proceeding, check that the VTN app is controlling Open vSwitch on the compute nodes.  Log
+into ONOS and run the `cordvtn-nodes` command:
+
+```
+$ ssh -p 8101 karaf@onos-cord   # password is karaf
+onos> cordvtn-nodes
+hostname=nova-compute, hostMgmtIp=192.168.122.177/24, dpIp=192.168.199.1/24, br-int=of:0000000000000001, dpIntf=veth1, init=COMPLETE
+Total 1 nodes
+```
+The important part is the `init=COMPLETE` at the end.  If you do not see this, refer to 
+[the CORD VTN page on the ONOS Wiki](https://wiki.onosproject.org/display/ONOS/CORD+VTN) for
+help fixing the problem.  This must be working to bring up VMs on the POD.
+
 Finally modify `cord-vtn-vsg.yml` and change `addresses_vsg` so that it contains the IP address block,
 gateway IP, and gateway MAC of the fabric.  (Again, the defaults are fine for the single-node POD.)
 Then run: