--- a/doc/ChangeLog	Sun Aug 27 20:38:52 2006 +0000
+++ b/doc/ChangeLog	Mon Aug 28 05:52:44 2006 +0000
@@ -1,3 +1,8 @@
+2006-08-28  Jim Meyering  <jim@meyering.net>
+
+	* visibility.texi: Actually read and correct the grammar of the
+	sentence affected by yesterday's change.
+
 2006-08-27  Jim Meyering  <jim@meyering.net>
 
 	* visibility.texi: Remove duplicate word: "pointer".

--- a/doc/visibility.texi	Sun Aug 27 20:38:52 2006 +0000
+++ b/doc/visibility.texi	Mon Aug 28 05:52:44 2006 +0000
@@ -1,6 +1,6 @@
 @c Documentation of gnulib module 'visibility'.
 
-@c Copyright (C) 2005 Free Software Foundation, Inc.
+@c Copyright (C) 2005, 2006 Free Software Foundation, Inc.
 
 @c Permission is granted to copy, distribute and/or modify this document
 @c under the terms of the GNU Free Documentation License, Version 1.2 or
@@ -41,8 +41,8 @@
 with @code{LD_PRELOAD}.) Whereas a call to a function for which the compiler
 can assume that it is in the same shared library is just a direct "call"
 instructions. Similarly for variables: A reference to a global variable
-fetches a pointer in the so-called GOT (global offset table); this pointer
-to the variable's memory. So the code to access it is two memory
+fetches a pointer in the so-called GOT (global offset table); this is a
+pointer to the variable's memory. So the code to access it is two memory
 load instructions. Whereas for a variable which is known to reside in the
 same shared library, it is just a direct memory access: one memory load
 instruction.