further documentation patches

[Bruce <bruce at puremagic dot com>]

Good morning,

Attached are 2 more documentation patches, one for libc/manual and one 
for libc/linuxthreads.  ChangeLog entries below.

Cheers,

  - Bruce

2001-05-25  Bruce Mitchener  <bruce@cubik.org>

         * manual/ctype.texi: Minor fix.
         * manual/install.texi: Likewise.
         * manual/startup.texi: Likewise.
         * manual/examples/dir.c: Use perror() rather than puts().

2001-05-25  Bruce Mitchener  <bruce@cubik.org>

         * linuxthreads.texi: Spelling corrections.
cvs server: Diffing .
Index: ctype.texi
===================================================================
RCS file: /cvs/glibc/libc/manual/ctype.texi,v
retrieving revision 1.24
diff -u -r1.24 ctype.texi
--- ctype.texi	2000/09/30 21:44:17	1.24
+++ ctype.texi	2001/05/25 17:26:20
@@ -679,7 +679,7 @@
 @deftp {Data Type} wctrans_t
 This data type is defined as a scalar type which can hold a value
 representing the locale-dependent character mapping.  There is no way to
-construct such a value apar from using the return value of the
+construct such a value apart from using the return value of the
 @code{wctrans} function.
 
 @pindex wctype.h
Index: install.texi
===================================================================
RCS file: /cvs/glibc/libc/manual/install.texi,v
retrieving revision 1.54
diff -u -r1.54 install.texi
--- install.texi	2001/05/14 07:36:15	1.54
+++ install.texi	2001/05/25 17:26:21
@@ -141,7 +141,7 @@
 @item --enable-omitfp
 Use maximum optimization for the normal (static and shared)
 libraries, and compile separate static libraries with debugging
-information and no optimisation.  We recommend against this.  The extra
+information and no optimization.  We recommend against this.  The extra
 optimization doesn't gain you much, it may provoke compiler bugs, and
 you won't be able to trace bugs through the C library.
 
Index: startup.texi
===================================================================
RCS file: /cvs/glibc/libc/manual/startup.texi,v
retrieving revision 1.46
diff -u -r1.46 startup.texi
--- startup.texi	2001/04/09 17:44:47	1.46
+++ startup.texi	2001/05/25 17:26:21
@@ -381,7 +381,7 @@
 an empty string, or points to a string containing a @code{=} character.
 It returns @code{0} if the call succeeded.
 
-This function was originall part of the BSD library but is now part of
+This function was originally part of the BSD library but is now part of
 the Unix standard.  The BSD version had no return value, though.
 @end deftypefun
 
cvs server: Diffing examples
Index: examples/dir.c
===================================================================
RCS file: /cvs/glibc/libc/manual/examples/dir.c,v
retrieving revision 1.2
diff -u -r1.2 dir.c
--- dir.c	1992/10/19 21:11:19	1.2
+++ dir.c	2001/05/25 17:26:22
@@ -19,7 +19,7 @@
       (void) closedir (dp);
     }
   else
-    puts ("Couldn't open the directory.");
+    perror ("Couldn't open the directory");
 
   return 0;
 }
Index: linuxthreads.texi
===================================================================
RCS file: /cvs/glibc/libc/linuxthreads/linuxthreads.texi,v
retrieving revision 1.12
diff -u -r1.12 linuxthreads.texi
--- linuxthreads.texi	2000/11/08 20:56:42	1.12
+++ linuxthreads.texi	2001/05/25 17:30:19
@@ -19,7 +19,7 @@
 * Thread Attributes::           Tuning thread scheduling.
 * Cancellation::                Stopping a thread before it's done.
 * Cleanup Handlers::            Deallocating resources when a thread is
-                                  cancelled.
+                                  canceled.
 * Mutexes::                     One way to synchronize threads.
 * Condition Variables::         Another way.
 * POSIX Semaphores::            And a third way.
@@ -102,12 +102,12 @@
 @deftypefun int pthread_join (pthread_t @var{th}, void **thread_@var{return})
 @code{pthread_join} suspends the execution of the calling thread until
 the thread identified by @var{th} terminates, either by calling
-@code{pthread_exit} or by being cancelled.
+@code{pthread_exit} or by being canceled.
 
 If @var{thread_return} is not @code{NULL}, the return value of @var{th}
 is stored in the location pointed to by @var{thread_return}.  The return
 value of @var{th} is either the argument it gave to @code{pthread_exit},
-or @code{PTHREAD_CANCELED} if @var{th} was cancelled.
+or @code{PTHREAD_CANCELED} if @var{th} was canceled.
 
 The joined thread @code{th} must be in the joinable state: it must not
 have been detached using @code{pthread_detach} or the
@@ -345,7 +345,7 @@
 @code{pthread_exit(PTHREAD_CANCELED)} was called.  All cleanup handlers
 are executed in reverse order, finalization functions for
 thread-specific data are called, and finally the thread stops executing.
-If the cancelled thread was joinable, the return value
+If the canceled thread was joinable, the return value
 @code{PTHREAD_CANCELED} is provided to whichever thread calls
 @var{pthread_join} on it. See @code{pthread_exit} for more information.
 
@@ -428,7 +428,7 @@
 
 The purpose of cleanup handlers is to free the resources that a thread
 may hold at the time it terminates. In particular, if a thread exits or
-is cancelled while it owns a locked mutex, the mutex will remain locked
+is canceled while it owns a locked mutex, the mutex will remain locked
 forever and prevent other threads from executing normally. The best way
 to avoid this is, just before locking the mutex, to install a cleanup
 handler whose effect is to unlock the mutex. Cleanup handlers can be
@@ -899,7 +899,7 @@
 @end deftypefun
 
 @code{pthread_cond_wait} and @code{pthread_cond_timedwait} are
-cancellation points. If a thread is cancelled while suspended in one of
+cancellation points. If a thread is canceled while suspended in one of
 these functions, the thread immediately resumes execution, relocks the
 mutex specified by  @var{mutex}, and finally executes the cancellation.
 Consequently, cleanup handlers are assured that @var{mutex} is locked