Typo/whitespace fixes

README.mkd

@@ -47,7 +47,7 @@ some uses in particular to keep in mind:
 * Alternate lexing/parsing frameworks
 * Including low-level code in high-level <br />
   (Think POST nodes in a PAST tree.  A more structured version of inline
-   nodes)
+   nodes.)
 * Compiling portions of a program.<br />
   (Given a PAST expression, return a POST expression not a full program.)
 
@@ -95,11 +95,11 @@ the ability to perform them should be kept in mind.
 
 ### Round-Trip Code
 
-The generating high quality code is difficult when the output of the
-compiler is opaque.  PASM is a mostly dead format and PIR is often derided
-for both the amount of hidden work it does and its compiler IMCC.  New
-assembly and intermediate formats are required.  These formats should be as
-easy to generate and process as possible.
+Generating high quality code is difficult when the output of the compiler
+is opaque.  PASM is a mostly dead format and PIR is often derided for both
+the amount of hidden work it does and its compiler IMCC.  New assembly and
+intermediate formats are required.  These formats should be as easy to
+generate and process as possible.
 
 The ability to store arbitrary objects in bytecode files means that not
 every PBC can be regenerated faithfully from disassembly, but handling the

TODO.mkd

@@ -24,8 +24,8 @@ around, starting from the bytecode and working our way up seems far more
 useful.  The implementation plan looks a little like this:
 
 * Build a set of classes that mirror packfile layout.
-	* Populated with PACT classes like Sub, Op, etc instead of
-	  PackfileConstantTable
+    * Populated with PACT classes like Sub, Op, etc instead of
+      PackfileConstantTable, etc
 * Make that able to produce bytecode and PIR
     * Register allocation
     * Stage structure

docs/compiling.mkd

@@ -58,8 +58,8 @@ points.  (Perhaps this should standardized to an array of strings.)
 
 ### Default Visit Methods
 
-Stages should generally through unknown types.  Obviously some stages will
-be more strict.
+Stages should generally pass through unknown types.  Obviously some stages
+will be more strict.
 
 	method visit(var node) {
 		return node;

docs/nodes.mkd

@@ -2,7 +2,7 @@
 
 PACT is based around the concept of tree transformations.  The High Level
 Language (HLL) handles parsing source text however it wants to and builds
-a PAST tree for PACT to handle.  That tree is converted into several
+as AST tree for PACT to handle.  That tree is converted into several
 intermediate forms before being turned into bytecode, PIR, or executed.
 
 Some level of organization is going to be needed for these.  This document