Update.

1999-01-24  Ulrich Drepper  <drepper@cygnus.com>

	* ctype/ctype.c (toupper): Correct variable names from lat change.
	(tolower): Likewise.

2 files changed, 11 insertions, 11 deletions

diff --git a/manual/install.texi b/manual/install.texi
index 0bc0be3ef3..694c1d69fa 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -251,10 +251,10 @@ One auxiliary program, @file{/usr/libexec/pt_chown}, is installed setuid
 sets the permissions on a pseudoterminal so it can be used by the
 calling process.  This means programs like @code{xterm} and
 @code{screen} do not have to be setuid to get a pty.  (There may be
-other reasons why they need privileges.)  If you are using a 2.1 Linux
-kernel with the @code{devptsfs} or @code{devfs} filesystems providing
-pty slaves, you don't need this program; otherwise you do.  The source
-for @file{pt_chown} is in @file{login/programs/pt_chown.c}.
+other reasons why they need privileges.)  If you are using a 2.1 or
+newer Linux kernel with the @code{devptsfs} or @code{devfs} filesystems
+providing pty slaves, you don't need this program; otherwise you do.
+The source for @file{pt_chown} is in @file{login/programs/pt_chown.c}.
 
 @node Tools for Compilation
 @appendixsec Recommended Tools for Compilation
diff --git a/manual/process.texi b/manual/process.texi
index 46aeff6009..14421b592f 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -243,15 +243,15 @@ signals and signal actions from the parent process.)
 @comment unistd.h
 @comment BSD
 @deftypefun pid_t vfork (void)
-The @code{vfork} function is similar to @code{fork} but on systems it
-is more efficient; however, there are restrictions you must follow to
+The @code{vfork} function is similar to @code{fork} but on some systems
+it is more efficient; however, there are restrictions you must follow to
 use it safely.
 
-While @code{fork} makes a complete copy of the calling process's
-address space and allows both the parent and child to execute
-independently, @code{vfork} does not make this copy.  Instead, the
-child process created with @code{vfork} shares its parent's address
-space until it calls exits or one of the @code{exec} functions.  In the
+While @code{fork} makes a complete copy of the calling process's address
+space and allows both the parent and child to execute independently,
+@code{vfork} does not make this copy.  Instead, the child process
+created with @code{vfork} shares its parent's address space until it
+calls @code{_exit} or one of the @code{exec} functions.  In the
 meantime, the parent process suspends execution.
 
 You must be very careful not to allow the child process created with