Index: doc/theses/andrew_beach_MMath/features.tex
===================================================================
--- doc/theses/andrew_beach_MMath/features.tex	(revision b041f11daf89e03f45478e73f7bf4f1f5d9806e2)
+++ doc/theses/andrew_beach_MMath/features.tex	(revision 13afd0cbeee1ddb3264d47bfd3555f7d1357ab72)
@@ -152,6 +152,6 @@
 % A type's descendants are its children and its children's descendants.
 
-For the purposes of illistration, a proposed -- but unimplemented syntax --
-will be used. Each virtual type is repersented by a trait with an annotation
+For the purposes of illustration, a proposed -- but unimplemented syntax --
+will be used. Each virtual type is represented by a trait with an annotation
 that makes it a virtual type. This annotation is empty for a root type, which
 creates a new tree:
@@ -192,5 +192,5 @@
 As @child_type@ is a child of @root_type@ it has the virtual members of
 @root_type@ (@to_string@ and @size@) as well as the one it declared
-(@irrelivant_function@).
+(@irrelevant_function@).
 
 It is important to note that these are virtual members, and may contain   
@@ -282,6 +282,6 @@
 
 Fields are filled in the same way as a structure as well. However an extra
-field is added, this field contains the pointer to the virtual table.
-It must be explicitly initialised by the user when the exception is
+field is added that contains the pointer to the virtual table.
+It must be explicitly initialized by the user when the exception is
 constructed.
 
@@ -310,10 +310,10 @@
 
 %\subsection{Exception Details}
-If one is only raising and handling exceptions, that is the only interface
-that is needed. However it is actually a short hand for a more complex
+This is the only interface needed when raising and handling exceptions.
+However it is actually a short hand for a more complex
 trait based interface.
 
-The language views exceptions through a series of traits,
-if a type satisfies them, then it can be used as an exception. The following
+The language views exceptions through a series of traits.
+If a type satisfies them, then it can be used as an exception. The following
 is the base trait all exceptions need to match.
 \begin{cfa}
@@ -322,5 +322,5 @@
 };
 \end{cfa}
-The trait is defined over two types, the exception type and the virtual table
+The trait is defined over two types: the exception type and the virtual table
 type. Each exception type should have a single virtual table type.
 There are no actual assertions in this trait because the trait system
@@ -347,5 +347,5 @@
 };
 \end{cfa}
-Both traits ensure a pair of types are an exception type, its virtual table
+Both traits ensure a pair of types is an exception type, its virtual table
 type
 and defines one of the two default handlers. The default handlers are used
@@ -393,5 +393,5 @@
 
 The differences between the two operations include how propagation is
-performed, where excecution after an exception is handler
+performed, where execution continues after an exception is handled
 and which default handler is run.
 
