X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Fvisibility.texi;h=881f33aa21cbfa932f86559742e78d2ad1efab89;hb=10d43fdb1b8394145a4e1a3e56df4ea7739dbb00;hp=07e88361c137487f6716f21dbf4e009142302029;hpb=a897449aaae8e6c051f3b9daaf984de5c5e092f3;p=gnulib.git

diff --git a/doc/visibility.texi b/doc/visibility.texi
index 07e88361c..881f33aa2 100644
--- 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,7 +41,7 @@ with the same name in the executable or in a shared library interposed
 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
+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