kc3-lang/freetype

diff --git a/docs/glyphs/glyphs-1.html b/docs/glyphs/glyphs-1.html
index ad945f7..9fd7e7d 100644
--- a/docs/glyphs/glyphs-1.html
+++ b/docs/glyphs/glyphs-1.html
@@ -151,12 +151,12 @@
       3. Character and font metrics
     </h3>
 
-    <p>Each glyph image is associated to various metrics which are used to
-    describe how must be placed and managed when rendering text.  Though
-    they are described in more details in section&nbsp;III, they relate to
-    glyph placement, cursor advances as well as text layout.  They are
-    extremely important to compute the flow of text when rendering a string
-    of text.</p>
+    <p>Each glyph image is associated with various metrics which are used to
+    describe how it must be placed and managed when rendering text.  These
+    are described in more details in section&nbsp;III; they relate to glyph
+    placement, cursor advances as well as text layout.  They are extremely
+    important to compute the flow of text when rendering a string of
+    text.</p>
 
     <p>Each scalable format also contains some global metrics, expressed in
     notional units, to describe some properties of all glyphs in the same
@@ -164,8 +164,8 @@
     the ascender, descender and text height for the font.</p>
 
     <p>Though these metrics also exist for non-scalable formats, they only
-    apply for a set of given character dimensions and resolutions, and
-    they are usually expressed in pixels then.</p>
+    apply for a set of given character dimensions and resolutions, and are
+    usually expressed in pixels.</p>
 
 
   <p><hr></p>
diff --git a/docs/glyphs/glyphs-2.html b/docs/glyphs/glyphs-2.html
index 3796831..dc2b2b9 100644
--- a/docs/glyphs/glyphs-2.html
+++ b/docs/glyphs/glyphs-2.html
@@ -62,13 +62,14 @@
   <tr bgcolor="#CCCCFF"
       valign=center><td>
     <h2>
-      II. Glyph mutlines
+      II. Glyph outlines
     </h2>
   </td></tr>
   </table>
 
-  <p>This section describes the way scalable representation of glyph images,
-  called outlines, are used by FreeType as well as client applications.</p>
+  <p>This section describes the way scalable representations of glyph
+  images, called outlines, are used by FreeType as well as client
+  applications.</p>
 
     <a name="section-1">
     <h3>
@@ -94,7 +95,7 @@
     <em>points</em>, rather than device-specific pixels.  Points are a
     simple <em>physical</em> unit, where 1&nbsp;point&nbsp;=&nbsp;1/72th of
     an inch, in digital typography.  As an example, most Roman books are
-    printed with a body text which size is chosen between 10 and
+    printed with a body text whose size is somewhere between 10 and
     14&nbsp;points.</p>
 
     <p>It is thus possible to compute the size of text in pixels from the
@@ -148,7 +149,7 @@
 
     <p>In creating the glyph outlines, a type designer uses an imaginary
     square called the <em>EM square</em>.  Typically, the EM square can be
-    thought of as a tablet on which the character are drawn.  The square's
+    thought of as a tablet on which the characters are drawn.  The square's
     size, i.e., the number of grid units on its sides, is very important for
     two reasons:</p>
 
@@ -218,7 +219,7 @@
 
     <p>As a consequence, proper glyph rendering needs the scaled points to
     be aligned along the target device pixel grid, through an operation
-    called <em>grid-fitting</em>, and often <em>hinting</em>.  One of its
+    called <em>grid-fitting</em> (often called<em>hinting</em>).  One of its
     main purposes is to ensure that important widths and heights are
     respected throughout the whole font (for example, it is very often
     desirable that the "I" and the "T" have their central vertical line of
@@ -255,9 +256,10 @@
         <p><em>automatic grid-fitting</em></p>
 
         <p>Some formats simply include no control information with each
-        glyph outline, apart metrics like the advance width and height.  It
-        is then up to the renderer to "guess" the more interesting features
-        of the outline in order to perform some decent grid-fitting.</p>
+        glyph outline, apart from metrics like the advance width and height. 
+        It is then up to the renderer to "guess" the more interesting
+        features of the outline in order to perform some decent
+        grid-fitting.</p>
       </li>
     </ul>
 
@@ -306,7 +308,7 @@
 
           <p><b>Size.</b> Glyph programs can be long.</p>
 
-          <p><b>Technicity.</b>
+          <p><b>Technical difficulty.</b>
           It is extremely difficult to write good hinting
           programs.  Very few tools available.</p>
         </td>
diff --git a/docs/glyphs/glyphs-3.html b/docs/glyphs/glyphs-3.html
index ee917ca..bec54e1 100644
--- a/docs/glyphs/glyphs-3.html
+++ b/docs/glyphs/glyphs-3.html
@@ -212,7 +212,7 @@
 
         <p>The horizontal distance from the current pen position to the
         glyph's left bbox edge.  It is positive for horizontal layouts, and
-        in most cases negative for vertical one.</p>
+        in most cases negative for vertical ones.</p>
       </li>
 
       <li>
@@ -220,7 +220,7 @@
 
         <p>The vertical distance from the baseline to the top of the glyph's
         bbox.  It is usually positive for horizontal layouts, and negative
-        for vertical ones</p>
+        for vertical ones.</p>
       </li>
 
       <li>
@@ -325,8 +325,8 @@
     <ul>
       <li>
         Because of hinting, simply scaling the font ascent or descent might
-        not give correct results.  A possible solution is to keepthe ceiling
-        of the scaled ascent, and floor of the scaled descent.
+        not give correct results.  A possible solution is to keep the
+        ceiling of the scaled ascent, and floor of the scaled descent.
       </li>
 
       <li>
diff --git a/docs/glyphs/glyphs-4.html b/docs/glyphs/glyphs-4.html
index 0bcc02c..37af040 100644
--- a/docs/glyphs/glyphs-4.html
+++ b/docs/glyphs/glyphs-4.html
@@ -78,7 +78,7 @@
       1. Kerning pairs
     </h3>
 
-    <p>Kerning consists in modifying the spacing between two successive
+    <p>Kerning consists of modifying the spacing between two successive
     glyphs according to their outlines.  For example, a "T" and a "y" can be
     easily moved closer, as the top of the "y" fits nicely under the upper
     right bar of the "T".</p>
diff --git a/docs/glyphs/glyphs-6.html b/docs/glyphs/glyphs-6.html
index 6a8e9e1..df98401 100644
--- a/docs/glyphs/glyphs-6.html
+++ b/docs/glyphs/glyphs-6.html
@@ -331,8 +331,8 @@
     </h3>
 
     <p>An outline point's vectorial coordinates are expressed in the
-    26.6&nbsp;format, i.e. in 1/64th of a pixel, hence coordinates
-    (1.0,-2.5) is stored as the integer pair (x:64,y:-192).</p>
+    26.6&nbsp;format, i.e. in 1/64th of a pixel, hence the coordinates
+    (1.0,-2.5) are stored as the integer pair (x:64,y:-192).</p>
 
     <p>After a master glyph outline is scaled from the EM grid to the
     current character dimensions, the hinter or grid-fitter is in charge of
diff --git a/docs/glyphs/glyphs-7.html b/docs/glyphs/glyphs-7.html
index b57ba06..381a98d 100644
--- a/docs/glyphs/glyphs-7.html
+++ b/docs/glyphs/glyphs-7.html
@@ -182,9 +182,9 @@
         <tt>num_grays</tt>
       </td>
       <td valign=top>
-        this is only used for "gray" pixel modes, it gives the number of
+        this is only used for "gray" pixel modes; it gives the number of
         gray levels used to describe the anti-aliased gray levels --
-        256&nbsp;by default with FreeType&nbsp;2
+        FreeType&nbsp;2 defaults to 256&nbsp;grays.
       </td>
     </tr>
     </table>