README.md

@@ -130,9 +130,9 @@ field, so it keeps drawing on its own. That one draw is also why two
 columns may not read overlapping reference *paths* — `{/cat.a}` beside
 `{/cat.a.b}` is refused, naming the fields to write instead, as
 [One draw, one spelling](#one-draw-one-spelling) refuses that pair inside a single
-format. A column may not reference the record it belongs to either: `{/users.first}`
+format. A column may not reference the record it belongs to by any spelling: `{/users.first}`
-inside `users` would contradict the `first` column beside it, so put a value two
+or a bare `{/users}` inside `users` describes a draw other than the columns beside
-columns share in its own category and reference that. A field hold, transform or
+it, so put a value two columns share in its own category and reference that. A field hold, transform or
 operand ties fields together within one column as always (see
 [Correlated fields](#correlated-fields) and [Decisions](#decisions)).
 

perf_test.go

@@ -52,7 +52,6 @@ func TestNoRenderAllocRegression(t *testing.T) {
 }
 
 // A record's fences read the compiled tree, so they belong to New, not to a draw.
-// A per-draw walk costs allocations in proportion to the tree.
 func TestNoRecordAllocRegression(t *testing.T) {
 	for _, s := range []struct{ name, json string }{
 		{"record 3 columns", `{"format":"","a":"x","b":"y","c":"z"}`},