diff --git a/wxPython/BUILD.osx.txt b/wxPython/BUILD.osx.txt
index d8dd33bd21..ce59e69df6 100644
--- a/wxPython/BUILD.osx.txt
+++ b/wxPython/BUILD.osx.txt
@@ -8,11 +8,10 @@ that you know your way around a command line and that you know how to
 get things from various CVS repositories as needed.
 
 
-1. "MacPython-OSX" 2.3 is required.  There is a disk image with an
-   installer package in the wxPython Sourceforge download area, in
-   this group:
+1. "MacPython-OSX" 2.3 is required.  If you don't have it already there is a disk image with an
+   installer package at
 
-   http://sourceforge.net/project/showfiles.php?group_id=10718&release_id=84730
+   http://homepages.cwi.nl/~jack/macpython/download.html
 
    If, for some reason you need to build your own Python, get the
    source from www.python.org and follow the instructions in the
@@ -34,7 +33,16 @@ get things from various CVS repositories as needed.
 3. Run configure from that build directory.
 
         cd build
-	../configure --with-mac --with-opengl --enable-debug
+	../configure --with-mac
+		     --with-opengl \
+		     --enable-geometry \
+                     --enable-optimise \
+		     --with-libjpeg=builtin \
+		     --with-libpng=builtin \
+		     --with-libtiff=builtin \
+
+   If you want to add code that activates various runtime checks and
+   assertion exceptions then add --enable-debug_flag.
 
 4. Make and install wxMac.
 
diff --git a/wxPython/BUILD.unix.txt b/wxPython/BUILD.unix.txt
index a2abfebb32..00f7ae94a5 100644
--- a/wxPython/BUILD.unix.txt
+++ b/wxPython/BUILD.unix.txt
@@ -6,7 +6,7 @@ directions for how to build wxPython the "new way."  This files
 describes the "old way" to build on unix-like systems.  The difference
 is very simple:  The new way uses a private copy of wxGTK while the
 old way uses either an existing wxGTK that may be installed and used
-by other apps, or you can build a wxGTK that will be accissible by
+by other apps, or you can build a wxGTK that will be accessable by
 other apps.
 
 
diff --git a/wxPython/BUILD.win32.txt b/wxPython/BUILD.win32.txt
index bbec92c2c7..3c55ece697 100644
--- a/wxPython/BUILD.win32.txt
+++ b/wxPython/BUILD.win32.txt
@@ -19,13 +19,13 @@ I use a tool called SWIG (http://www.swig.org) to help generate the
 C++ sources used in the wxPython extension module.  However you don't
 need to have SWIG unless you want to modify the *.i files.  I've made
 several modifications to SWIG specific to wxPython's needs and so the
-modified sources are included in the wx CVS at.../wxPython/wxSWIG.
+modified sources are included in the wx CVS at .../wxPython/wxSWIG.
 But because of the size and since most people won't need it my SWIG is
 not included in the wxPythonSrc tarball.  You'll need to get it from
 CVS or a CVS snapshot.
 
-If you need to modify the *.i files for wxPython then change to this
-directory and run:
+If you need to modify the *.i files for wxPython then change to the
+.../wxPython/wxSWIG directory and run:
 
       nmake -f makefile.vc
 
@@ -119,7 +119,6 @@ C. Change to the %WXWIN%\include\wx\msw directory and copy setup0.h to
          wxUSE_TREELAYOUT		0
 	 wxUSE_MS_HTML_HELP		0
          wxUSE_POSTSCRIPT		1
-	 wxUSE_DYNLIB_CLASS		1
 
 
     ** NEW **
diff --git a/wxPython/README.txt b/wxPython/README.txt
index 5e3c5b2f0a..910ed12481 100644
--- a/wxPython/README.txt
+++ b/wxPython/README.txt
@@ -19,18 +19,18 @@ and to play with as a learning exercise.
 The next thing you should do is join the wxPython-users maillist where
 you can interact with a community of other users and developers who
 are willing to help you learn, answer questions and solve problems.
-To join the mail list just send an email message to the following
-address from the account you want to receive the mail messages from
-the list:
+To join the mail list just go to this web page and follow the
+instructions there:
 
-    wxPython-users-subscribe@lists.wxwindows.org
+	     http://wxpython.org/maillist.php
 
 There is also a good set of class reference documentation available
 for wxPython, but currently it is geared for the C++ user.  This may
 be a little daunting at first, but with a little practice you'll
-easily be able to "translate" from the C++ shown there to Python.  Not
-all classes documented are available in Python, but most of the GUI
-related classes are.
+easily be able to "mentally translate" from the C++ shown into Python.
+(See http://wiki.wxpython.org/index.cgi/C_2b_2bGuideForwxPythoneers
+for a little help on this process.) Not all classes documented are
+available in Python, but most of the GUI related classes are.
 
 
 Other Info
diff --git a/wxPython/distrib/README.1st.txt b/wxPython/distrib/README.1st.txt
index 9fcdf827a7..ba13d95633 100644
--- a/wxPython/distrib/README.1st.txt
+++ b/wxPython/distrib/README.1st.txt
@@ -130,7 +130,7 @@ Clear as mud?  Good.  Let's get started.
    wxPython and you are running on Solaris and building with gcc, then
    you may be able to work around the problem by uncommenting a bit of
    code in setup.py and building again.  Look for 'SunOS' in setup.py
-   and uncomment the block following it.  The problem is that Sun's ld
+   and uncomment the block containing it.  The problem is that Sun's ld
    does not automatically add libgcc to the link step.
 
 7. That's all, except for the having fun part!
diff --git a/wxPython/setup.py b/wxPython/setup.py
index 5d5957aa54..6635823122 100755
--- a/wxPython/setup.py
+++ b/wxPython/setup.py
@@ -483,7 +483,7 @@ elif os.name == 'posix':
     libdirs = []
     libs = []
 
-    # If you get unresolved symbol errors on Solaris and are usign gcc, then
+    # If you get unresolved symbol errors on Solaris and are using gcc, then
     # uncomment this block to add the right flags to the link step and build
     # again.
     ## if os.uname()[0] == 'SunOS':