2000-03-09 Martin Buchholz <martin@xemacs.org>

	* sysdeps/unix/sysv/linux/alpha/syscall.S:
	* manual/message.texi (Using gettextized software):
	* manual/message.texi (Message Translation): Doc Fixes.
	* manual/filesys.texi (File Size):
	* manual/charset.texi (glibc iconv Implementation):
	* locale/programs/ld-collate.c (collate_output):
	* iconv/gconv_db.c (find_derivation):
	* manual/install.texi:
	* manual/search.texi (Hash Search Function):
	* manual/stdio.texi (Output Conversion Syntax):
	* FAQ.in:
	* config.h.in:
	* sysdeps/generic/dl-sysdep.c:
	Doc Fixes.  `allows to' is not correct English.

	* elf/rtld.c: Doc fixes.
	* manual/creature.texi (Feature Test Macros): Doc fixes.
	* manual/memory.texi (Hooks for Malloc): Doc Fixes.

	* manual/filesys.texi (Working Directory): Check for ERANGE to
	avoid infloop.

1 files changed, 3 insertions, 3 deletions

diff --git a/manual/install.texi b/manual/install.texi
index c4d58a7b34..33fb985166 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -52,9 +52,9 @@ GNU Make, and possibly others.  @xref{Tools for Compilation}, below.
 GNU libc can be compiled in the source directory, but we strongly advise to
 build it in a separate build directory.  For example, if you have unpacked
 the glibc sources in @file{/src/gnu/glibc-2.1.0}, create a directory
-@file{/src/gnu/glibc-build} to put the object files in.  This allows to
-remove the whole build directory in case an error occurs which is the
-safest way to get a clean way and should always be done.
+@file{/src/gnu/glibc-build} to put the object files in.  This allows
+removing the whole build directory in case an error occurs, which is the
+safest way to get a fresh start and should always be done.
 
 From your object directory, run the shell script @file{configure} found
 at the top level of the source tree.  In the scenario above, you'd type