Index: subversion/bindings/swig/INSTALL
===================================================================
--- subversion/bindings/swig/INSTALL	(revision 20817)
+++ subversion/bindings/swig/INSTALL	(working copy)
@@ -126,7 +126,10 @@
        of .c source files.  It will then compile and link those .c files into
        Python libraries.)
 
-   2.  Run 'make install-swig-py' (as root, typically)
+   2.  Run 'make check-swig-py' from the top of the Subversion source
+       tree, to test the bindings 
+
+   3.  Run 'make install-swig-py' (as root, typically)
        from the top of the Subversion source tree.  This will copy
        your new Python libraries into the appropriate system location.
 
@@ -140,7 +143,7 @@
        example of doing this for building rpms looks like
        'make install-swig-py DESTDIR=$RPM_BUILD_ROOT/usr'.
 
-   3.  Make sure that whatever directory the bindings got installed in
+   4.  Make sure that whatever directory the bindings got installed in
        is in your PYTHONPATH.  That directory depends on how you
        installed; a typical location is /usr/local/lib/svn-python/.
 
@@ -321,6 +324,12 @@
 
 *  Python
 
+   The Python bindings are using the standard module testing facilities
+   to do regression tests. Simply run 'make check-swig-py' as described in
+   the install section.
+
+   You can also adopt the following methods to test the bindings:
+
    1.  Verify that an 'svn' package has been installed correctly.  You can
        do this by running Python via 'python -c "from svn import client"'.
 
@@ -340,8 +349,8 @@
 *  Perl
 
    The Perl bindings are using the standard module testing facilities
-   to do regression tests. Simply run make check-swig-pl as described in the
-   install section.
+   to do regression tests. Simply run 'make check-swig-pl' as described in 
+   the install section.
 
 * Ruby