diff --git a/doc/source/vol2to3.rst b/doc/source/vol2to3.rst
index e768df0c2..2520562a6 100644
--- a/doc/source/vol2to3.rst
+++ b/doc/source/vol2to3.rst
@@ -27,7 +27,7 @@ The object model has changed as well, objects now inherit directly from their Py
 object is actually a Python integer (and has all the associated methods, and can be used wherever a normal int could).
 In Volatility 2, a complex proxy object was constructed which tried to emulate all the methods of the host object, but
 ultimately it was a different type and could not be used in the same places (critically, it could make the ordering of
-operations important, since a + b might not work, but b + a might work fine).
+operations important, since x + y might not work, but y + x might work fine).
 
 Volatility 3 has also had significant speed improvements, where Volatility 2 was designed to allow access to live memory
 images and situations in which the underlying data could change during the run of the plugin, in Volatility 3 the data
@@ -56,15 +56,14 @@ Volatility 2 were strictly limited to a stack, one on top of one other.  In Vola
 
 Automagic
 ---------
-In Volatility 2, we often tried to make this simpler for both users and developers.  This resulted in something was
-referred to as automagic, in that it was magic that happened automatically.  We've now codified that more, so that the
+In Volatility 2, we often tried to make this simpler for both users and developers.  This resulted in something referred to as automagic, in that it was magic that happened automatically.  We've now codified that more, so that the
 automagic processes are clearly defined and can be enabled or disabled as necessary for any particular run.  We also
 included a stacker automagic to emulate the most common feature of Volatility 2, automatically stacking address spaces
 (now translation layers) on top of each other.
 
-By default the automagic chosen to be run are determined based on the plugin requested, so that linux plugins get linux
-specific automagic and windows plugins get windows specific automagic.  This should reduce unnecessarily searching for
-linux kernels in a windows image, for example.  At the moment this is not user configurableS.
+By default the automagic chosen to be run are determined based on the plugin requested, so that Linux plugins get Linux
+specific automagic and Windows plugins get Windows specific automagic.  This should reduce unnecessarily searching for
+Linux kernels in a Windows image, for example.  At the moment this is not user configurable.
 
 Searching and Scanning
 ----------------------