From 39399791a3f638d8f584908ce0772eab76faf497 Mon Sep 17 00:00:00 2001
From: Dustin Mitchell <djmitche@users.sourceforge.net>
Date: Sun, 23 Jan 2000 21:45:42 +0000
Subject: [PATCH] Grammatical changes

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@145 626c5289-ae23-0410-ae9c-e8d60b6d4f22
---
 Doc/whitepaper.html | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/Doc/whitepaper.html b/Doc/whitepaper.html
index 4425da5c7..94a44057b 100644
--- a/Doc/whitepaper.html
+++ b/Doc/whitepaper.html
@@ -80,7 +80,7 @@ easier to do the following:
 <ul>
 <li>Build user interfaces to existing software.  For example, the
 primary reason for Swig's emphasis on scripting languages is not that
-scripting languages are cool (which they are), it is that interpreters
+scripting languages are cool (which they are). It is that interpreters
 make great user interfaces for a wide variety of applications.
 Furthermore, interpreters can be used to build more advanced user
 interfaces using toolkits such as Tk.
@@ -173,7 +173,7 @@ to the user community and people who want to write modules.
 <p>
 <li><b>Why stop at C and scripting?</b>.  Although SWIG does a great
 job of building scripting interfaces, there is no practical reason to
-restrict it's functionality in this way.  For one, it is probably
+restrict its functionality in this way.  For one, it is probably
 worthwhile to consider alternative input languages including Fortran
 and CORBA IDL.  Second, there are a variety of secondary tasks that
 one might be able to do with such a system such as analyze the
@@ -183,8 +183,9 @@ software.   Although these sound like lofty goals, I believe that the system
 should be flexible enough to allow such applications.
 </ul>
 
-Of course, the real trick is how one goes about solving these issues without
-making Swig excessively complicated--both from the point of development and use.
+Of course, the real trick is how one goes about solving these issues
+without making Swig excessively complicated--both from the point of
+development and use.
 
 <h2>3. SWIG Redevelopment: Modules</h2>
 
@@ -310,7 +311,7 @@ fully support all of C++ (at least not initially).
 <p>
 <li><b>SWIM</b>. The SWIG Monitor.  This is utility module that allows users to browse
 through internal compiler data structures using a web browser.  This is primarily intended
-for development purposes, but which may evolve into a general purpose interface browsing
+for development purposes, but may evolve into a general purpose interface browsing
 tool.
 
 <p>