--- a/README.markdown	Sat Mar 19 19:53:12 2011 -0500
+++ b/README.markdown	Sat Mar 19 20:00:04 2011 -0500
@@ -57,16 +57,16 @@
 in how it operates. This is sufficient for most cases, but please be aware of
 the following limitations.
 
-1. Ensure your class (or struct) definition is all on one line:
+1.  Ensure your class (or struct) definition is all on one line:
 
          class my_unit_test : public fructose::test_base<my_unit_test>
 
-   If you split the above across multiple lines `fructose_gen.py` will not
-   recognize your class and will not generate a test instance for it.
+    If you split the above across multiple lines `fructose_gen.py` will not
+    recognize your class and will not generate a test instance for it.
 
-2. `fructose_gen.py` does not understand C-style comments or the preprocessor.
-   To comment out a test, you can either use C++ comments, or change the function
-   name slightly to ensure it won't be recognized. Examples:
+2.  `fructose_gen.py` does not understand C-style comments or the preprocessor.
+    To comment out a test, you can either use C++ comments, or change the function
+    name slightly to ensure it won't be recognized. Examples:
 
           /*
           ** void test_is_sorted(const std::string& name)  // this won't work
@@ -80,7 +80,7 @@
           // void test_is_sorted(const std::string& name)    // this works
           // FRUCTOSE_TEST(is_sorted)                        // this works
 
-   The above also applies to commenting out test classes.
+    The above also applies to commenting out test classes.
 
 
 Support