Some small spelling errors and clarification based on recent events.

diff --git a/INSTALL.win32 b/INSTALL.win32
index 5bd817c778443c46936a49b9e7750b138ca9172d..2d75a10d43e5311829f0ea5bc6d429f17f2c35ab 100644 (file)
--- a/INSTALL.win32
+++ b/INSTALL.win32
@@ -1,4 +1,4 @@
-$Id: INSTALL.win32,v 1.23 2004/02/29 14:35:10 gbazin Exp $
+$Id$
 
 INSTALL file for the Windows9x/Me/NT4/2k/XP version of the VLC media player
 
@@ -26,33 +26,33 @@ Building VLC from the source code
 If you want to build VLC from sources, you can do it in several ways:
 
 - natively on Windows, using cygwin (www.cygwin.com) with or without the
-  unix emulation layer. This is the prefered way to compile vlc if you want
+  POSIX emulation layer. This is the preferred way to compile vlc if you want
   to do it on Windows.
-  NOTE: This is the PREFERED way of building VLC natively (the others
+  NOTE: This is the PREFERRED way of building VLC natively (the others
   are not as much tested so expect more difficulties with them).
 
 - natively on Windows, using MSYS+MINGW (www.mingw.org)
-  (MSYS is a minimal build environnement to compile unixish projects under
-  windoze. It provides all the common unix tools like sh, gmake...)
+  (MSYS is a minimal build environnement to compile Unixish projects under
+  windoze. It provides all the common Unix tools like sh, gmake...)
   Please note that the gettext utilities are not included in the default
   MSYS/MINGW packages so you won't be able to build VLC with i18n support.
 
 - natively on Windows, using Microsoft Visual C++. Even though we provide some
   msvc project files with vlc, this method is advised only if you just want to
-  experiment/play with some basic functionnalities in vlc. The reason for this
+  experiment/play with some basic functionality in vlc. The reason for this
   is that vlc depends on a lot of 3rd party libraries and building them in
   MSVC is not convenient and sometimes even impossible.
   ( NOTE: if you want to run vlc under the msvc debugger, you need to run it
     with the --fast-mutex --win9x-cv-method=1 options because the debugger
     usually loses signals sent by PulseEvent() )
 
-- or on Linux, using the mingw32 cross-compiler.
+- or on GNU/Linux, using the mingw32 cross-compiler.
 
 Getting the right compiler tools
 ================================
 
 - cross-compiling with mingw32:
-You first need to download a linux cross-compiler version of mingw32.
+You first need to download a GNU/Linux cross-compiler version of mingw32.
 
 For Debian GNU/Linux users, you can use the mingw32, mingw32-binutils and
 mingw32-runtime packages.
@@ -79,7 +79,7 @@ http://prdownloads.sf.net/mingw/MSYS-1.0.9.exe
 http://prdownloads.sf.net/mingw/MinGW-3.0.0-rc3.exe
 http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe
 
-Getting the additionnal libraries
+Getting the additional libraries
 =================================
 
 VLC depends on other libraries to provide some features like ac3 audio decoding
@@ -95,9 +95,14 @@ We also provide a package with all the libraries already compiled so it is
 actually really easy to compile a full-featured version of vlc (these compiled
 libraries will only work with mingw or cygwin):
 http://download.videolan.org/pub/testing/win32/contrib-20040229-win32-bin-gcc3.3.1-only.tar.bz2
+
 All you need to do is extract it in your root directory (the include files
 and libraries will be put in /usr/win32). You can do this with the following
-command: "tar xjvf contrib-20040229-win32-bin-gcc3.3.1-only.tar.bz2 -C /"
+command: 
+
+  tar xjvf contrib-20040229-win32-bin-gcc3.3.1-only.tar.bz2 -C /
+
+Please note the "-C /". 
 
 A complete list of the libraries on which we depend can be found here:
 http://developers.videolan.org/vlc/
@@ -160,9 +165,11 @@ along those lines:
       --disable-cddax --disable-vcdx \
       --enable-debug
 
-If you are using cygwin, you can build VLC with or without the unix emulation
-layer (without is usually better). To build without the emulaion layer, use
-something like this:
+If you are using cygwin, you can build VLC with or without the POSIX
+emulation layer. Without is usually better and with POSIX emulation
+hasn't been tested in about a year or so. So to build without the
+emulation layer, use something like this:
+
   ./bootstrap && \
   CPPFLAGS="-I/usr/win32/include -I/usr/win32/include/ebml" \
   LDFLAGS=-L/usr/win32/lib \
@@ -185,7 +192,7 @@ something like this:
       --enable-debug
 
 If you want to use the emulation layer, then just omit the CC="gcc -mno-cygwin"
-CXX="g++ -mno-cygwin" line.
+CXX="g++ -mno-cygwin" line. You're on your own though.
 
 If you are compiling with MSYS/MINGW, then you can use something along those
 lines: