Misc doc updates

README.md

@@ -4,20 +4,19 @@
 
 - Clean up my 'parent vertex mapping' thingy, *and* come up with
   meaningful terms to discuss it.
-- Terminology: "run" a rule versus "evaluate" a rule.
 - Do transforms compose in the *reverse* of automata_scratch? This
   appears to be the case.
 
 ## Important but less critical:
 
 - Why must I repeat myself so much in these definitions?
+- Docs on modules
 - Consider trampolining `to_mesh`.  My call stack seems needlessly
   deep in spots.  Can I make tail-recursive?
 - Grep for all TODOs in code, really.
 - Look at everything in README.md in automata_scratch.
 - Implement some of the tougher examples from the above too, e.g. the
   triple nested spiral.  See `examples.py`.
-- Actual Rust-style docs!
 
 ## If I'm bored:
 

src/examples.rs

@@ -243,8 +243,6 @@ fn ram_horn() -> RuleStep {
         faces: vec![
             Tag::Parent(0), Tag::Parent(2), Tag::Parent(1),
             Tag::Parent(0), Tag::Parent(3), Tag::Parent(2),
-            // TODO: Parent in 'final_geom' refers always to vertices
-            // in 'geom' - right?
         ],
     };
     RuleStep {
@@ -260,6 +258,30 @@ fn ram_horn() -> RuleStep {
     }
 }
 
+/*
+fn ram_horn_branch() -> RuleStep {
+    
+}
+ */
+
+/*
+pub fn twist() -> RuleStep {
+    let ang=0.1;
+    let dz=0.2;
+    let dx0=2;
+    let count=4;
+    let scale=0.98;
+
+    let seed = vec![
+        vertex(-0.5, -0.5, 0),
+        vertex(-0.5,  0.5, 0),
+        vertex( 0.5,  0.5, 0),
+        vertex( 0.5, -0.5, 0),        
+    ];
+    
+}
+ */
+
 pub fn main() {
 
     let run_test = |r: Rule, iters, name| {