<i>personalities.</i> An exception handling personality is defined by way of a
<i>personality function</i> (ex. for C++ <tt>__gxx_personality_v0</tt>) which
receives the context of the exception, an <i>exception structure</i> containing
-the exception object type and value, and a reference the exception table for the
-current function. The personality function for the current compile unit is
+the exception object type and value, and a reference to the exception table for
+the current function. The personality function for the current compile unit is
specified in a <i>common exception frame</i>.</p>
<p>The organization of an exception table is language dependent. For C++, an
<div class="doc_text">
-<p>A call within the scope of a try statement can potential raise an exception.
+<p>A call within the scope of a try statement can potentially raise an exception.
In those circumstances, the LLVM C++ front-end replaces the call with an
<tt>invoke</tt> instruction. Unlike a call, the invoke has two potential
continuation points; where to continue when the call succeeds as per normal, and
<p>The term used to define a the place where an invoke continues after an
exception is called a <i>landing pad</i>. LLVM landing pads are conceptually
-alternative entry points into where a exception structure reference and a type
+alternative function entry points where a exception structure reference and a type
info index are passed in as arguments. The landing pad saves the exception
structure reference and then proceeds to select the catch block that corresponds
to the type info of the exception object.</p>