# HG changeset patch
# User Jim Meyering <jim@meyering.net>
# Date 1156744364 0
# Node ID 85aa09b61c066aee680da873edc3faf2e4c80cec
# Parent  510edb12693811fd0d680a9467f181f1c8e31e5b
* visibility.texi: Actually read and correct the grammar of the
sentence affected by yesterday's change.

diff --git a/doc/ChangeLog b/doc/ChangeLog
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -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".
diff --git a/doc/visibility.texi b/doc/visibility.texi
--- a/doc/visibility.texi
+++ b/doc/visibility.texi
@@ -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.