--- a/README.QNX	Sat Aug 23 23:18:49 2003 +0000
+++ b/README.QNX	Sat Aug 23 23:20:21 2003 +0000
@@ -1,112 +1,108 @@
 README by Mike Gorchak <mike@malva.ua>, <lestat@i.com.ua>
-Last changed at 29 Jul 2003.
+Last changed at 12 Aug 2003.
 
-=========================================================================
+======================================================================
 OpenGL:
 
-    OpenGL in window mode  works well  and  stable, in fullscreen
-mode too, but fullscreen mode has not been heavily tested yet.
-    If you have QNX RtP version 6.1.0 and above you must download
-new Photon3D runtime from http://developers.qnx.com or install it
-from public repository or from public CD, available with QNX. The
-versions of OS before 6.1.0 are not supported.
-    While  creating  OpenGL  context  software  renderer  mode is
-artificially selected (QSSL  made  acceleration  only for  Voodoo
-boards in fullscreen mode, sorry but I  don't have  this board to
-test OpenGL - maybe it work or maybe not :)). If you want accele-
-ration - you may remove some line in source code: find  the  file
-SDL_ph_video.c and remove the following
+    OpenGL works well and is stable, but fullscreen mode has not  been
+heavily tested yet.
+    If you have QNX RtP version 6.1.0 or above you must  download  the
+Photon3D runtime from http://developers.qnx.com or install it from the
+public repository or the  public CD, available  with  QNX. OS versions
+below 6.1.0 are not supported.
+    When creating an OpenGL context, software renderer mode is artifi-
+cially selected (QSSL made acceleration  only  for  Voodoo  boards  in
+fullscreen mode, sorry but I don't have this board  to  test  OpenGL -
+maybe it works or maybe not :)). If you  want  acceleration - you  can
+remove one line in the source code: find the  file SDL_ph_video.c  and
+remove the following
 
     OGLAttrib[OGLargc++]=PHOGL_ATTRIB_FORCE_SW;
      
-line in the ph_SetupOpenGLContext() function or  change  argument
-to the PHOGL_ATTRIB_FORCE_HW or PHOGL_ATTRIB_FAVOR_HW.
+line in the ph_SetupOpenGLContext() function or change the argument to
+PHOGL_ATTRIB_FORCE_HW or PHOGL_ATTRIB_FAVOR_HW.
 
-=========================================================================
-Wheel and multibutton mouses:
+======================================================================
+Wheel and multi-button mouses:
 
-    Photon emitting keyboard events (key up and down) when  moved
-mouse wheel. But key_scan field appears valid according to flags,
-and it contain zero. It is base method of detecting  mouse  wheel
-events under photon. It looks like a hack, but it works for me :)
-on different PC configurations.
+    Photon emits  keyboard  events (key up and down)  when  the  mouse
+wheel is moved. The key_scan field appears valid, and it contains zero.
+That is a basic method of detecting  mouse  wheel events under Photon.
+It looks like a hack, but it works for me :) on various PC  configura-
+tions.
 
-I'm tested it on:
+I've tested it on:
 
 1. Genius Optical NetScroll/+ (1 wheel)
-2. A4Tech Optical GreatEye WheelMouse, model: WOP-35. (2 wheels +
-   2 additional buttons). Wheel for vertical scrolling  works  as
-   usual, but second wheel for horizontal scrolling emitting  two
-   consequented events up or down, so it can  provide  more  fast
-   scrolling then the  first  wheel. Additional  buttons  doesn't
-   emitting any events, but its look like  handled by  photon  in
-   unusual way - like click to front, but works not with any win-
-   dow, looks like bug-o-feature :).
+2. A4Tech Optical  GreatEye  WheelMouse,  model: WOP-35. (2 wheels + 2
+   additional buttons). The wheel for vertical scrolling works as usu-
+   al, but the second wheel for horizontal scrolling emits two sequen-
+   tial events up or down, so it can provide faster scrolling than the
+   first wheel. Additional buttons don't emit any events, but it looks
+   like they're handled by photon in an unusual  way - like  click  to
+   front, but works not with any window, looks like bug-o-feature :).
 
-=========================================================================
+======================================================================
 CDROM handling issues:
 
-    Access to CDROM can be provided only with 'root'  previleges.
-I can't do anything with this fact. /dev/cd0 have  the brw-------
-flags and root:root rights.
+    Access to CDROM can only be  provided  with  'root'  privileges. I
+can't do anything about that, /dev/cd0 has brw------- permissions  and
+root:root rights.
 
-=========================================================================
+======================================================================
 Video Overlays:
 
-    Overlays can flickering during the window movement, resizing,
-etc. It happens because photon driver  updates  the  real  window
-contents behind the overlay, then draws the temporary  chroma key
-color over window contents. It can be done without the chroma key
-using but it cause overlay will be  always  on top. So flickering
-during the movement much better in that case.
-    Double buffering code temporary disabled in the photon driver
-code, beacuse on my GF2-MX it  cause  accidently  buffer  switch,
-which going to the old frame showing. S3 Savage3D have  the  same
-problem, but ATI Rage 128 has not this problem. I think it can be
-fixed later. Current code works very fine, so maybe double buffe-
-ring is not needed right now.
-    Something strange appears when you tried to move window  with
-overlay beyond the left border of the screen. Overlay  trying  to
-stay at position x=0, but when tried to move  it  a  bit  more it
-jumps  at  posituin  x=-60. Really  strange, looks  like  overlay
-doesn't love the negotive coordinates.
+    Overlays can flicker  during  window  movement,  resizing, etc. It
+happens because the photon driver updates the real window contents be-
+hind the overlay, then draws the temporary chroma key color  over  the
+window contents. It can be done without using the chroma key but  that
+causes the overlay to always be on top. So  flickering  during  window
+movement is preferred instead.
+    Double buffering code is temporarily disabled in the photon driver
+code, because on my GF2-MX it can accidentally cause a buffer  switch,
+which causes the old frame to show. S3 Savage4 has the  same  problem,
+but ATI Rage 128 doesn't. I think it can be fixed later. Current  code
+works very well, so maybe double buffering is not needed right now.
+    Something strange happens when you try to move the window with the
+overlay beyond the left border  of the screen. The  overlay  tries  to
+stay at position x=0, but when attempting to move it  a  bit  more  it
+jumps to position x=-60 (on GF2-MX, on ATI Rage128 this  value  a  bit
+smaller). It's really strange, looks  like  the  overlay  doesn't like
+negative coordinates.
 
-=========================================================================
+=======================================================================
 Shared library building:
 
-    Shared  library can be  built, but before  running autogen.sh
-script you  need  manually  delete  the  libtool  m4  stuff  from
-the acinclude.m4 file (it comes after ESD  detection  code  up to
-end of the file). Because libtool stuff in the  acinclude.m4 file
-very old and doesn't know anything about the QNX. Just  remove it
-and run autogen.sh script.
+    A shared library can be built, but before running  the  autogen.sh
+script you must manually delete the libtool.m4 stuff from the acinclu-
+de.m4 file (it comes after the ESD detection code up to the end of the
+file), because the libtool stuff in the acinclude.m4 file is very  old
+and doesn't know anything about QNX. Just remove it and run autogen.sh.
 
-=========================================================================
+======================================================================
 Some building issues:
 
-    Feel free to not pass --disable-shared option  to  configure,
-if you read comment above about 'Shared library building'. Other-
-wise this option is strongly  recomended, because  the sdl-config
-script will be unfunctional.
+    Feel free to not use the --disable-shared configure option if you'
+ve read the above comment about 'Shared  library  building'. Otherwise
+this  option  is  strongly  recommended, as  without it the sdl-config
+script will be broken.
 
-    Run configure script without x11 support, e.g.:
+    Run the configure script without x11 support, e.g.:
 
     a) for OpenGL support:
-    ./configure --prefix=/usr/local \
+    ./configure --prefix=/usr       \
                 --disable-video-x11 \
                 --disable-shared
 
     b) without OpenGL support:
-    ./configure --prefix=/usr/local \
+    ./configure --prefix=/usr       \
                 --disable-video-x11 \
                 --disable-shared    \
                 --disable-video-opengl
 
-    In test directory  also run  ./configure  script  without x11
-support, e.g.:
+    In the test directory also run the ./configure script without
+x11 support, e.g.:
 
-    ./configure  --with-sdl-prefix=/usr/local      \
-                 --with-sdl-exec-prefix=/usr/local \
-                 --prefix=/usr/local --without-x
-
-
+    ./configure  --with-sdl-prefix=/usr            \
+                 --with-sdl-exec-prefix=/usr       \
+                 --prefix=/usr --without-x