* visibility.texi: Remove duplicate word: "pointer".

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 27f4e939e2b64bd231e7fff69801b92a1492762b..77d336f9cc265d75a544939db2455379299c14a1 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2006-08-27  Jim Meyering  <jim@meyering.net>
+
+       * visibility.texi: Remove duplicate word: "pointer".
+
 2006-08-15  Paul Eggert  <eggert@cs.ucla.edu>
 
        * regexprops-generic.texi: Add a copyright notice.

diff --git a/doc/visibility.texi b/doc/visibility.texi
index 07e88361c137487f6716f21dbf4e009142302029..285236100d172e91bc9e4e1fc1863e9cbc6ec181 100644 (file)
--- a/doc/visibility.texi
+++ b/doc/visibility.texi
@@ -42,7 +42,7 @@ 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
-pointer to the variable's memory. So the code to access it is two memory
+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.