minor updates

diff --git a/docs/xlibdriver.html b/docs/xlibdriver.html
index 7734542dcb9137d79c91ccdf2936893e5096782c..6bb6532533b4bb7926db4e0bae0883bb13f4d1ab 100644 (file)
--- a/docs/xlibdriver.html
+++ b/docs/xlibdriver.html
@@ -22,7 +22,7 @@ software-only drivers.
 
 <p>
 Since the Xlib driver <em>emulates</em> the GLX extension, it's not
-totally conformance with a true GLX implementation.
+totally conformant with a true GLX implementation.
 The differences are fairly obscure, however.
 </p>
 
@@ -31,7 +31,7 @@ The unique features of the Xlib driver follows.
 </p>
 
 
-<H2>X Display Modes</H2>
+<H2>X Visual Selection</H2>
 <p>
 Mesa supports RGB(A) rendering into almost any X visual type and depth.
 </p>
@@ -68,7 +68,7 @@ Here are some examples:
 </pre>
 
 
-<H2>Double buffering</H2>
+<H2>Double Buffering</H2>
 <p>
 Mesa can use either an X Pixmap or XImage as the backbuffer when in
 double buffer mode.  Using GLX, the default is to use an XImage.  The
@@ -107,7 +107,7 @@ significant.
 </p>
 
 
-<H2>Gamma correction</H2>
+<H2>Gamma Correction</H2>
 <p>
 To compensate for the nonlinear relationship between pixel values
 and displayed intensities, there is a gamma correction feature in
@@ -171,11 +171,12 @@ SERVER_OVERLAY_VISUALS property:
 </pre>
 
 
-<H2>HPCR glClear(GL_COLOR_BUFFER_BIT) dithering</H2>
+<H2>HPCR Dithering</H2>
 <p>
 If you set the <b>MESA_HPCR_CLEAR</b> environment variable then dithering
 will be used when clearing the color buffer.  This is only applicable
 to HP systems with the HPCR (Color Recovery) feature.
+This incurs a small performance penalty.
 </p>