follow-up typos

Doc/Manual/CSharp.html

@@ -2751,7 +2751,7 @@ public class ExtendMe : global::System.IDisposable {
 <P>
 C# enums use int as the underlying type for each enum item.
 If you wish to change the underlying type to something else, then use the <tt>csbase</tt> typemap.
-For example when your C++ code uses a value larget than int, this is necessary as the C# compiler will not compile values which are too large to fit into an int.
+For example when your C++ code uses a value larger than int, this is necessary as the C# compiler will not compile values which are too large to fit into an int.
 Here is an example:
 </p>
 

Doc/Manual/Extending.html

@@ -278,7 +278,7 @@ or <tt>perl5.swg</tt>.
 </p>
 
 <p>
-As a debugging aide, the text that SWIG feeds to its C++ parser can be
+As a debugging aid, the text that SWIG feeds to its C++ parser can be
 obtained by running <tt>swig -E interface.i</tt>.  This output
 probably isn't too useful in general, but it will show how macros have
 been expanded as well as everything else that goes into the low-level

Doc/Manual/Go.html

@@ -611,7 +611,7 @@ work is necessary.
 </p>
 
 <p>
-This subchapter gives a step by step guide how to properly sublass a C++ class
+This subchapter gives a step by step guide how to properly subclass a C++ class
 with a Go type.  In general it is strongly recommended to follow this guide
 completely to avoid common pitfalls with directors in Go.
 </p>

Doc/Manual/Java.html

@@ -3877,7 +3877,7 @@ Or target all wrapped methods using:
 This tells SWIG to generate a C++ catch handler using some code from the <a href="Typemaps.html#Typemaps_throws_typemap">throws typemap</a> for <tt>Swig::DirectorException</tt> that SWIG supplies by default, see <a href="SWIGPlus.html#SWIGPlus_catches">Exception handling with %catches</a>.
 This typemap code is written to simply catch the C++ <tt>Swig::DirectorException</tt> class and immediately
 return to Java throwing the original Java exception that it has stored.
-The net result is a stack trace containing the original Java exception including the location that the exception was thown from.
+The net result is a stack trace containing the original Java exception including the location that the exception was thrown from.
 </p>
 
 <div class="shell">

Doc/Manual/Lisp.html

@@ -650,7 +650,7 @@ swig -clisp -module <i>module-name</i>   <i>file-name</i>
     generated by SWIG may not be absolutely correct, and you may need
     to modify them. The good thing is that you don't need to complex 
     interface file for the CLISP module. The CLISP module tries to
-    produce code which is both human readable and easily modifyable.
+    produce code which is both human readable and easily modifiable.
 </p>
 <H3><a name="Lisp_nn9">28.3.1 Additional Commandline Options </a></H3>
 

Doc/Manual/Typemaps.html

@@ -1360,7 +1360,7 @@ Below is a list of the typical default types supplied by language modules, showi
 %typemap(in) SWIGTYPE *            { ... default pointer handling ...                         };
 %typemap(in) SWIGTYPE *const       { ... default pointer const handling ...                   };
 %typemap(in) SWIGTYPE *const&      { ... default pointer const reference handling ...         };
-%typemap(in) SWIGTYPE[ANY]         { ... 1D fixed size arrays handlling ...                   };
+%typemap(in) SWIGTYPE[ANY]         { ... 1D fixed size arrays handling ...                    };
 %typemap(in) SWIGTYPE []           { ... unknown sized array handling ...                     };
 %typemap(in) enum SWIGTYPE         { ... default handling for enum values ...                 };
 %typemap(in) const enum SWIGTYPE & { ... default handling for const enum reference values ... };