Merge branch 'sunoru-master'

* sunoru-master:
  Correct some whitespace changes
  Realign for some comments.
  Fix some typos in docs and examples and make the code look nicer.

Doc/Manual/Chicken.html

@@ -295,9 +295,9 @@
 
       <p>
       The author of TinyCLOS, Gregor Kiczales, describes TinyCLOS as:
-      "Tiny CLOS is a Scheme implementation of a `kernelized' CLOS, with a
+      "Tiny CLOS is a Scheme implementation of a 'kernelized' CLOS, with a
       metaobject protocol. The implementation is even simpler than
-      the simple CLOS found in `The Art of the Metaobject Protocol,'
+      the simple CLOS found in 'The Art of the Metaobject Protocol',
       weighing in at around 850 lines of code, including (some)
       comments and documentation."
       </p>

Doc/Manual/Extending.html

@@ -2537,7 +2537,7 @@ also return a pointer to the base class (<tt>Language</tt>) so that only the int
 Save the code for your language module in a file named "<tt>python.cxx</tt>" and
 place this file in the <tt>Source/Modules</tt> directory of the SWIG distribution.
 To ensure that your module is compiled into SWIG along with the other language modules,
-modify the file <tt>Source/Modules/Makefile.am</tt> to include the additional source
+modify the file <tt>Source/Makefile.am</tt> to include the additional source
 files.  In addition, modify the file <tt>Source/Modules/swigmain.cxx</tt>
 with an additional command line option that activates the module. Read the source---it's straightforward.
 </p>

Doc/Manual/SWIG.html

@@ -750,7 +750,7 @@ form of type-checking however).</p>
 <p>
 For enumerations, it is critical that the original enum definition be
 included somewhere in the interface file (either in a header file or
-in the <tt>%{,%}</tt> block). SWIG only translates the enumeration
+in the <tt>%{ %}</tt> block). SWIG only translates the enumeration
 into code needed to add the constants to a scripting language. It
 needs the original enumeration declaration in order to get the correct
 enum values as assigned by the C compiler.
@@ -3442,7 +3442,7 @@ header files.
 <p>
 Sometimes, it is necessary to use certain header files in order for
 the code generated by SWIG to compile properly. Make sure you
-include certain header files by using a <tt>%{,%}</tt> block like this:
+include certain header files by using a <tt>%{ %}</tt> block like this:
 </p>
 
 <div class="code"><pre>

Examples/python/class/index.html

@@ -86,7 +86,7 @@ Note: when creating a C++ extension, you must run SWIG with the <tt>-c++</tt> op
 
 <h2>A sample Python script</h2>
 
-Click <a href="example.py">here</a> to see a script that calls the C++ functions from Python.
+Click <a href="runme.py">here</a> to see a script that calls the C++ functions from Python.
 
 <h2>Key points</h2>
 

Examples/python/constants/index.html

@@ -17,7 +17,7 @@ to see a SWIG interface with some constant declarations in it.
 
 <h2>Accessing Constants from Python</h2>
 
-Click <a href="example.py">here</a> to see a script that prints out the values
+Click <a href="runme.py">here</a> to see a script that prints out the values
 of the constants contained in the above file.
 
 <h2>Key points</h2>

Examples/python/enum/index.html

@@ -19,7 +19,7 @@ of enumerated types are handled as integers.
 <ul>
 <li><a href="example.h">example.h</a>.  Header file containing some enums.
 <li><a href="example.i">example.i</a>.  Interface file.
-<li><a href="example.py">example.py</a>. Sample Python script.
+<li><a href="runme.py">runme.py</a>. Sample Python script.
 </ul>
 
 <h2>Notes</h2>

Examples/python/funcptr/index.html

@@ -65,7 +65,7 @@ Here are some files that illustrate this with a simple example:
 <li><a href="example.c">example.c</a>
 <li><a href="example.h">example.h</a>
 <li><a href="example.i">example.i</a> (SWIG interface)
-<li><a href="example.py">example.py</a> (Sample script)
+<li><a href="runme.py">runme.py</a> (Sample script)
 </ul>
 
 <h2>Notes</h2>

Examples/python/pointer/index.html

@@ -145,7 +145,7 @@ extraction.
 <ul>
 <li> <a href="example.c">example.c</a>  (C Source)
 <li> <a href="example.i">example.i</a>  (SWIG interface)
-<li> <a href="example.py">example.py</a> (Python Script)
+<li> <a href="runme.py">runme.py</a> (Python Script)
 </ul>
 
 <h2>Notes</h2>

Examples/python/reference/index.html

@@ -121,7 +121,7 @@ Click <a href="example.i">here</a> to see a SWIG interface file with these addit
 
 <h2>Sample Python script</h2>
 
-Click <a href="example.py">here</a> to see a script that manipulates some C++ references.
+Click <a href="runme.py">here</a> to see a script that manipulates some C++ references.
 
 <h2>Notes:</h2>
 

Examples/python/simple/index.html

@@ -65,7 +65,7 @@ to create the extension <tt>examplemodule.so</tt>.
 
 <h2>Using the extension</h2>
 
-Click <a href="example.py">here</a> to see a script that calls our C functions from Python.
+Click <a href="runme.py">here</a> to see a script that calls our C functions from Python.
 
 <h2>Key points</h2>
 

Examples/python/variables/index.html

@@ -48,7 +48,7 @@ double foo;
 </blockquote>
 
 it will be accessed in the Python module as <tt>cvar.foo</tt>. Click
-<a href="example.py">here</a> to see a script that updates and prints
+<a href="runme.py">here</a> to see a script that updates and prints
 out the values of the variables using this technique.
 
 <h2>Key points</h2>