(Mutexes and Condition Variables): Change

`flag' to `flags' in docstring.

diff --git a/doc/ref/ChangeLog b/doc/ref/ChangeLog
index 9a4e3be..9aa92d6 100644 (file)
--- a/doc/ref/ChangeLog
+++ b/doc/ref/ChangeLog
@@ -1,3 +1,11 @@
+2008-03-24  Neil Jerram  <neil@ossau.uklinux.net>
+
+       Applying patch from Julian Graham, containing minor fixes to his
+       thread enhancements:
+       
+       * api-scheduling.texi (Mutexes and Condition Variables): Change
+       `flag' to `flags' in docstring.
+
 2008-03-19  Neil Jerram  <neil@ossau.uklinux.net>
 
        * api-debug.texi (Low Level Trap Calls): Removed (material

diff --git a/doc/ref/api-scheduling.texi b/doc/ref/api-scheduling.texi
index 7f40506..ec136fb 100644 (file)
--- a/doc/ref/api-scheduling.texi
+++ b/doc/ref/api-scheduling.texi
@@ -377,7 +377,7 @@ in all threads is one way to avoid such problems.
 @sp 1
 @deffn {Scheme Procedure} make-mutex . flags
 @deffnx {C Function} scm_make_mutex ()
-@deffnx {C Function} scm_make_mutex_with_flags (SCM flag)
+@deffnx {C Function} scm_make_mutex_with_flags (SCM flags)
 Return a new mutex.  It is initially unlocked.  If @var{flags} is 
 specified, it must be a list of symbols specifying configuration flags
 for the newly-created mutex.  The supported flags are: