[PATCH] Doc fixes

[Yoshiki Hayashi <yo...@xemacs.org>]

Yes, it's doc fixes again. :-)

Index: subversion/include/svn_fs.h
===================================================================
RCS file: /cvs/subversion/subversion/include/svn_fs.h,v
retrieving revision 1.49
diff -u -r1.49 svn_fs.h
--- subversion/include/svn_fs.h	2001/02/19 05:59:36	1.49
+++ subversion/include/svn_fs.h	2001/02/26 08:58:30
@@ -387,7 +387,7 @@
 /* Abort the transaction TXN.  Any changes made in TXN are discarded,
    and the filesystem is left unchanged.
 
-   If the commit succeeds, it frees TXN, and any temporary resources
+   If the abort succeeds, it frees TXN, and any temporary resources
    it holds.  Any root objects referring to TXN's root directory
    become invalid; performing any operation on them other than closing
    them will produce an SVN_ERR_FS_DEAD_TRANSACTION error.  */
Index: subversion/tests/TEST-FRAMEWORK
===================================================================
RCS file: /cvs/subversion/subversion/tests/TEST-FRAMEWORK,v
retrieving revision 1.2
diff -u -r1.2 TEST-FRAMEWORK
--- subversion/tests/TEST-FRAMEWORK	2001/01/31 02:47:00	1.2
+++ subversion/tests/TEST-FRAMEWORK	2001/02/26 08:58:33
@@ -21,10 +21,10 @@
 doesn't give us good control of results reporting.  (Specifically, we
 can't stop it from spamming the terminal.)
 
-Instead, our Makefile.am's contain a SVN_TEST_PROGRAMS variable (a
+Instead, our Makefile.am's contain a SVN_TESTS variable (a
 list of programs to run), and a home-made `check' target.
 
-A `make check` will run each program in SVN_TEST_PROGRAMS and only
+A `make check` will run each program in SVN_TESTS and only
 print a description *if a test fails*.  All test results are logged to
 a file called `tests.log'.
 


-- 
Yoshiki Hayashi