commit cc6b4435458b5db6aed17631e4789c43d21ee8e5
author Dean Troyer <dtroyer@gmail.com> Mon Apr 08 15:38:03 2013 -0500
committer Dean Troyer <dtroyer@gmail.com> Tue Apr 09 14:05:32 2013 -0500
tree a8460f062f571849a7a9a547c85771d625828b34
parent 2e75ff1a41e741ee77926a1262e1e9410701b4e1

Formatting cleanups, doc updates and whatnot

Change-Id: Ica8298353be22f947c8e8a03d8dc29ded9cb26dd

README.md

diff --git a/README.md b/README.md
index d8538c2..6570a14 100644
--- a/README.md
+++ b/README.md
@@ -120,14 +120,16 @@
     # Optional, to enable tempest configuration as part of devstack
     enable_service tempest
 
-Then run stack.sh as normal.
+Then run `stack.sh` as normal.
+
+# Tempest
 
 If tempest has been successfully configured, a basic set of smoke tests can be run as follows:
 
     $ cd /opt/stack/tempest
     $ nosetests tempest/tests/network/test_network_basic_ops.py
 
-Multi-Node Setup
+# Multi-Node Setup
 
 A more interesting setup involves running multiple compute nodes, with Quantum networks connecting VMs on different compute nodes.
 You should run at least one "controller node", which should have a `stackrc` that includes at least: