--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2007-03-19  Ben Pfaff  <blp@gnu.org>
+
+	* doc/gnulib.texi: Fix typos.
+	Suggested by Thien-Thi Nguyen <ttn@gnuvola.org>.
+
 2007-03-19  Paul Eggert  <eggert@cs.ucla.edu>
 
 	* lib/getcwd.c (__getcwd): Remove redundant comparison of buf to NULL.

--- a/doc/gnulib.texi
+++ b/doc/gnulib.texi
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
-@comment $Id: gnulib.texi,v 1.33 2007-03-15 22:58:36 eggert Exp $
+@comment $Id: gnulib.texi,v 1.34 2007-03-19 20:30:25 blp Exp $
 @comment %**start of header
 @setfilename gnulib.info
 @settitle GNU Gnulib
@@ -7,7 +7,7 @@
 @syncodeindex pg cp
 @comment %**end of header
 
-@set UPDATED $Date: 2007-03-15 22:58:36 $
+@set UPDATED $Date: 2007-03-19 20:30:25 $
 
 @copying
 This manual is for GNU Gnulib (updated @value{UPDATED}),
@@ -202,16 +202,16 @@
 handling happens in rare situations, but performing the out of memory
 error handling after almost all API function invocations pollute your
 source code and might make it harder to spot more serious problems.
-The strategy chosen improve code readability and robustness.
+The strategy chosen improves code readability and robustness.
 
 @cindex Aborting execution
 For most applications, aborting the application with an error message
-when the out of memory situation occur is the best that can be wished
+when the out of memory situation occurs is the best that can be wished
 for.  This is how the library behaves by default.
 
 @vindex xalloc_fail_func
 However, we realize that some applications may not want to have the
-GSS library abort execution in any situation.  The GSS library support
+GSS library abort execution in any situation.  The GSS library supports
 a hook to let the application regain control and perform its own
 cleanups when an out of memory situation has occurred.  The application
 can define a function (having a @code{void} prototype, i.e., no return