18. Merged in XFree86 code up to 4.4.0 including changes to files that had

    a changed license. There was only one change which happened to be from
    me (Egbert Eich).

1 files changed, 13 insertions, 13 deletions

diff --git a/README.sgml b/README.sgml
index ba081fd..edb7f31 100644
--- a/README.sgml
+++ b/README.sgml
@@ -20,8 +20,8 @@ graphics chipsets. The following chipsets are supported:
 <itemize>
 <item> 6422
 
-	Old chipset. The driver is still very unstable, including computer
-	crashes. You would prefer using XFree86 3.3.x for this chipset.
+	Old chipset. The driver is still very unstable and has computer
+	crashes. You should use XFree86 3.3.x for this chipset.
 
 
 <item> AT24
@@ -63,16 +63,16 @@ Full DGA 2.0 support with framebuffer access and drawing acceleration.
 
 <sect> Video
 <p>
-A limited hardware support for video decoding on AT24 and AT25/3D. It can
-display an image in YUV colours inside the desktop. There are some more exotic
-formats (YUV 4.1.1, YUV 4.0.0, RGB 8,16.32bpp).
+It has limited hardware support for video decoding on the AT24 and AT25/3D. It can
+also display an image in YUV colours inside the desktop. There are some more exotic
+formats such as YUV 4.1.1, YUV 4.0.0 and RGB 8,16.32bpp.
 
 <sect> Shadow framebuffer
 <p>
-There is a mode, called shadow framebuffer, where the graphics is only used
+There is a mode, called shadow framebuffer, where the graphics are used
 to display the images. All rendering is done in memory in a so-called shadow
 framebuffer. This mode is useful if you need lots of reading in the video
-memory. You will have to put
+memory and to use it you will have to put
 <verb>
   Option "ShadowFB"
 </verb>
@@ -81,7 +81,7 @@ in your XF86Config file.
 
 <sect> Configuration
 <p>
-First: Please run the xf86config program to create a correct
+First: Run the xf86config program to create a correct
 configuration.
 
 You can turn off hardware cursor by inserting the following line in the
@@ -101,12 +101,12 @@ Or turn off MMIO
   Option "nolinear"
 </verb>
 
-Please don't specify the amount of video RAM you have or which chipset
-you have in the config file, let the driver probe for this. Also please
+Do not specify either the amount of video RAM or which chipset
+in the config file.  It is better to let the driver probe for this. Also 
 don't put any "clocks" line in the device section since these chips have
-a fully programmable clock that can take (almost) any modeline you throw
-at it. It might fail at some specific clock values but you should just
-try a slightly different clock and it should work.
+a fully programmable clock that can almost take any modeline you throw
+at it. It might though  fail at some specific clock values but in that case 
+you should just try a slightly different clock and it should work.
 
 <sect> glide2x
 <p>