fix docs, path provided by Olly

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@9047 626c5289-ae23-0410-ae9c-e8d60b6d4f22

Doc/Manual/Modules.html

@@ -169,7 +169,7 @@ a <tt>Derived</tt> instance and call the wrapper for <tt>Base::method</tt>.
 
 <p>
 <b>%feature("compactdefaultargs")</b><br>
-This feature can reduce the number of wrapper methods when wrapping methods with default arguments. The section on <a href="SWIGPlus.html#SWIGPlus_default_args">default arguments</a> discusses the feature and it's limitations.
+This feature can reduce the number of wrapper methods when wrapping methods with default arguments. The section on <a href="SWIGPlus.html#SWIGPlus_default_args">default arguments</a> discusses the feature and its limitations.
 </p>
 
 </body>

Doc/Manual/Python.html

@@ -1021,7 +1021,7 @@ dereference the pointer from Python. Of course, that isn't much of a concern in
 In older versions of Swig (1.3.22 or older), pointers were represented
 using a plain string object. If you have an old package that still
 requires that representation, or you just feel nostalgic, you can
-always retreive it by casting the pointer object to a string:
+always retrieve it by casting the pointer object to a string:
 </p>
 
 <div class="targetlang"><pre>
@@ -4583,7 +4583,7 @@ class object (if applicable).
 <p>
 Using docstrings in Python code is becoming more and more important
 and more tools are coming on the scene that take advantage of them,
-everything from full-blown documentaiton generators to class browsers
+everything from full-blown documentation generators to class browsers
 and popup call-tips in Python-aware IDEs.  Given the way that SWIG
 generates the proxy code by default, your users will normally get
 something like <tt>"function_name(*args)"</tt> in the popup calltip of

Doc/Manual/SWIGPlus.html

@@ -822,7 +822,7 @@ public:
 
 <p>
 SWIG handles default arguments by generating an extra overloaded method for each defaulted argument.
-SWIG is effectively handling methods with default arguments as if it had wrapped the equivalent overloaded methods.
+SWIG is effectively handling methods with default arguments as if it was wrapping the equivalent overloaded methods.
 Thus for the example above, it is as if we had instead given the following to SWIG:
 </p>
 
@@ -839,7 +839,7 @@ public:
 
 <p>
 The wrappers produced are exactly the same as if the above code was instead fed into SWIG.
-Details of this is covered later in the <a href="#SWIGPlus_overloaded_methods">Wrapping Overloaded Functions and Methods</a> section.
+Details of this are covered later in the <a href="#SWIGPlus_overloaded_methods">Wrapping Overloaded Functions and Methods</a> section.
 This approach allows SWIG to wrap all possible default arguments, but can be verbose.
 For example if a method has ten default arguments, then eleven wrapper methods are generated.
 </p>