Update.

	* manual/charset.texi: Fix typos.  Rephrase.
	* manual/process.texi: Likewise.
	* manual/signal.texi: Likewise.
	Patches by Mike Coleman <mkc@kc.net>.

diff --git a/ChangeLog b/ChangeLog
index b34074f..8fd070f 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2000-03-21  Ulrich Drepper  <drepper@redhat.com>
 
+       * manual/charset.texi: Fix typos.  Rephrase.
+       * manual/process.texi: Likewise.
+       * manual/signal.texi: Likewise.
+       Patches by Mike Coleman <mkc@kc.net>.
+
        * libio/oldtmpfile.c: Use new macros from shlib-compat.h to define
        versions.
        * libio/iofdopen.c: Likewise.

diff --git a/manual/charset.texi b/manual/charset.texi
index f48db7d..de4bc7e 100644 (file)
--- a/manual/charset.texi
+++ b/manual/charset.texi
@@ -628,8 +628,8 @@ string pointed to by @var{pwc}.  The conversion is performed according
 to the locale currently selected for the @code{LC_CTYPE} category.  If
 the conversion for the character set used in the locale requires a state
 the multibyte string is interpreted in the state represented by the
-object pointed to by @var{ps}.  If @var{ps} is a null pointer an static,
-internal state variable used only by the @code{mbrtowc} variable is
+object pointed to by @var{ps}.  If @var{ps} is a null pointer, a static,
+internal state variable used only by the @code{mbrtowc} function is
 used.
 
 If the next multibyte character corresponds to the NUL wide character
@@ -729,7 +729,7 @@ Otherwise the multibyte character sequence is invalid and the return
 value is @code{(size_t) -1}.
 
 The multibyte sequence is interpreted in the state represented by the
-object pointer to by @var{ps}.  If @var{ps} is a null pointer an state
+object pointed to by @var{ps}.  If @var{ps} is a null pointer, a state
 object local to @code{mbrlen} is used.
 
 @pindex wchar.h

diff --git a/manual/process.texi b/manual/process.texi
index 08c880b..b9f2551 100644 (file)
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -63,9 +63,8 @@ possible to create the shell process, and otherwise is the status of the
 shell process.  @xref{Process Completion}, for details on how this
 status code can be interpreted.
 
-If the @var{command} argument is a null pointer, a non-zero return value
-indicates that a command processor is available and this function can be
-used at all.
+If the @var{command} argument is a null pointer, a return value of zero
+indicates that no command processor is available.
 
 This function is a cancelation point in multi-threaded programs.  This
 is a problem if the thread allocates some resources (like memory, file

diff --git a/manual/signal.texi b/manual/signal.texi
index 000bcb9..95e7a36 100644 (file)
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -187,7 +187,7 @@ When a signal terminates a process, its parent process can determine the
 cause of termination by examining the termination status code reported
 by the @code{wait} or @code{waitpid} functions.  (This is discussed in
 more detail in @ref{Process Completion}.)  The information it can get
-includes the fact that termination was due to a signal, and the kind of
+includes the fact that termination was due to a signal and the kind of
 signal involved.  If a program you run from a shell is terminated by a
 signal, the shell typically prints some kind of error message.
 
@@ -1040,15 +1040,15 @@ a handler for @code{SIGKILL} or @code{SIGSTOP}.
 @end table
 @end deftypefun
 
-@strong{Compatibility Note:} A problem when working with the
-@code{signal} function is that it has a different semantic on BSD and
-SVID system.  The difference is that on SVID systems the signal handler
-is deinstalled after an signal was delivered.  On BSD systems the
+@strong{Compatibility Note:} A problem encountered when working with the
+@code{signal} function is that it has different semantics on BSD and
+SVID systems.  The difference is that on SVID systems the signal handler
+is deinstalled after signal delivery.  On BSD systems the
 handler must be explicitly deinstalled.  In the GNU C Library we use the
 BSD version by default.  To use the SVID version you can either use the
 function @code{sysv_signal} (see below) or use the @code{_XOPEN_SOURCE}
-feature select macro (@pxref{Feature Test Macros}).  Generally it should
-be avoided to use this functions due to the compatibility problems.  It
+feature select macro (@pxref{Feature Test Macros}).  In general, use of these
+functions should be avoided because of compatibility problems.  It
 is better to use @code{sigaction} if it is available since the results
 are much more reliable.
 
@@ -1082,7 +1082,7 @@ main (void)
 @end smallexample
 
 @noindent
-Note how if a given signal was previously set to be ignored, this code
+Note that if a given signal was previously set to be ignored, this code
 avoids altering that setting.  This is because non-job-control shells
 often ignore certain signals when starting children, and it is important
 for the children to respect this.