kc3-lang/freetype

diff --git a/ChangeLog b/ChangeLog
index 711aa04..d7916ff 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,10 +1,11 @@
 2002-04-11  David Turner  <david@freetype.org>
 
-        * README, docs/CHANGES, Jamfile.in: updating for the 2.1.0 release
+	* README, docs/CHANGES: Updates for the 2.1.0 release.
+	* Jamfile.in: New file.
 
-2002-04-11  Maxim Shemanarev <mcseemagg@yahoo.com>
+2002-04-11  Maxim Shemanarev  <mcseemagg@yahoo.com>
 
-        * src/smooth/ftgrays.c (gray_hline): very minor optimization. :-)
+	* src/smooth/ftgrays.c (gray_hline): Minor optimization.
 
 2002-04-02  Werner Lemberg  <wl@gnu.org>
 
diff --git a/Jamfile.in b/Jamfile.in
index 9272ffd..f12c13f 100644
--- a/Jamfile.in
+++ b/Jamfile.in
@@ -1,4 +1,4 @@
-# FreeType 2 top Jamfile (c) 2001 David Turner
+# FreeType 2 top Jamfile (c) 2001, 2002 David Turner
 #
 
 # We need to invoke a SubDir rule if the FT2 source directory top is not the
@@ -16,8 +16,8 @@ FT2_SRC     = [ FT2_SubDir src ] ;
 FT2_LIB     = $(LIBPREFIX)freetype ;
 
 
-# We don't support libtool just yet. It seems that this is not
-# so simple with Jam, but I'll study this topic later..
+# We don't support libtool just yet.  It seems that this is not
+# so simple with Jam, but I'll study this topic later.
 #
 
 # used only when trying to debug the hinter(s)
diff --git a/docs/CHANGES b/docs/CHANGES
index 069159b..e4a8dde 100644
--- a/docs/CHANGES
+++ b/docs/CHANGES
@@ -1,18 +1,18 @@
-LATESET CHANGES BETWEEN 2.0.9 and 2.0.8
+LATEST CHANGES BETWEEN 2.0.9 and 2.0.8
 
   I. IMPORTANT BUG FIXES
   
-    - Certain fonts, like "foxjump.ttf" contain broken name tables with
+    - Certain fonts like "foxjump.ttf" contain broken name tables with
       invalid entries and wild offsets.  This caused FreeType to crash when
       trying to load them.
       
-      The SFNT 'name' table loader has been fixed to be able to support
+      The SFNT `name' table loader has been fixed to be able to support
       these strange fonts.
 
       Moreover, the code in charge of processing this table has been changed
-      to always favor Windows-formatted entries over other ones.  Hence, a
+      to always favour Windows-formatted entries over other ones.  Hence, a
       font that works on Windows but not on the Mac will load cleanly in
-      FreeType and report accurate values for Family & Postscript names.
+      FreeType and report accurate values for Family & PostScript names.
 
     - The CID font driver has been fixed.  It unfortunately returned a
       Postscript Font name with a leading slash, as in
@@ -20,37 +20,38 @@ LATESET CHANGES BETWEEN 2.0.9 and 2.0.8
 
     - FreeType 2 should now compile fine on AIX 4.3.3 as a shared library.
 
-    - A bug in the Postscript hinter has been found and fixed. You shouldn't
-      be experimenting un-even stem widths at small pixel sizes (like 14-17).
+    - A bug in the Postscript hinter has been found and fixed, removing
+      un-even stem widths at small pixel sizes (like 14-17).
       
-      This improves the quality of a certain number of Postscript fonts :o)
+      This improves the quality of a certain number of Postscript fonts.
 
 
-  II. NEW FEATURES:
+  II. NEW FEATURES
 
-    - A new function named FT_Library_Version has been added to return
-      the current library's major, minor and patch version numbers. This
-      is important since the macros FREETYPE_MAJOR, FREETYPE_MINOR and
+    - A new function named `FT_Library_Version' has been added to return
+      the current library's major, minor, and patch version numbers.  This
+      is important since the macros FREETYPE_MAJOR, FREETYPE_MINOR, and
       FREETYPE_PATCH cannot be used when the library is dynamically linked
-      by a program..
+      by a program.
 
-    - Two new APIs have been added: FT_Get_First_Char and FT_Get_Next_Char.
+    - Two new APIs have been added: `FT_Get_First_Char' and
+      `FT_Get_Next_Char'.
     
       Together, these can be used to iterate efficiently over the currently
       selected charmap of a given face.  Read the API reference for more
       details.
 
 
-  III. MISCELLANEOUS:
+  III. MISCELLANEOUS
   
     - The FreeType sources are under heavy internal re-factoring.  As a
       consequence, we have created a branch named "STABLE" on the CVS to
       hold all future releases/fixes in the 2.0.x family.
       
       The HEAD branch now contains the re-factored sources and shouldn't be
-      used for testing or packaging new releases.  In the cases where you
-      would like to access the 2.0.9 sources from our CVS repository, you
-      should use the tag VER-2-0-9.
+      used for testing or packaging new releases.  In case you would like
+      to access the 2.0.9 sources from our CVS repository, use the tag
+      `VER-2-0-9'.
 
 
 ============================================================================
@@ -62,14 +63,13 @@ LATEST CHANGES BETWEEN 2.0.8 and 2.0.7
     - There was a small but nasty bug in "freetype-config.in" which
       caused the "freetype-config" script to fail on Unix.
       
-      this doesn't prevented the installation of the library or even
+      This didn't prevent the installation of the library or even
       its execution, but caused problems when trying to compile many
-      Unix packages that depend on it.. !!!
+      Unix packages that depend on it.
       
-
-    - some TrueType or OpenType fonts embedded in PDF documents do
+    - Some TrueType or OpenType fonts embedded in PDF documents do
       not have a 'cmap', 'post' and 'name' as is required by the
-      specification, FreeType no longer refuses to load such fonts..
+      specification.  FreeType no longer refuses to load such fonts.
 
     - various fixes to the PCF font driver
     
diff --git a/docs/FTL.txt b/docs/FTL.txt
index e9c0d9b..c422629 100644
--- a/docs/FTL.txt
+++ b/docs/FTL.txt
@@ -43,17 +43,16 @@ Introduction
   assume no liability related to The FreeType Project.
 
 
-  Finally, many people asked us for a preffered form a credit/disclaimer
-  to use in compliance with this license. We thus encourage you to use the
-  following text:
+  Finally,  many  people  asked  us  for  a  preferred  form  for  a
+  credit/disclaimer to use in compliance with this license.  We thus
+  encourage you to use the following text:
 
    """  
     Portions of this software are copyright © 1996-2002 The FreeType Project 
-    (www.freetype.org). All Rights Reserved
+    (www.freetype.org).  All rights reserved.
    """
 
 
-
 Legal Terms
 ===========