(Create Tags Table): Clean up previous change.

diff --git a/man/ChangeLog b/man/ChangeLog
index ee19a3254be202494be024d98ab2845a428fa389..8a5eb243616368662492dd79ed691ef922dbbd31 100644 (file)
--- a/man/ChangeLog
+++ b/man/ChangeLog
@@ -1,3 +1,7 @@
+2007-05-06  Richard Stallman  <rms@gnu.org>
+
+       * maintaining.texi (Create Tags Table): Clean up previous change.
+
 2007-05-05  Francesco Potort\e,Al\e(B  <pot@gnu.org>
 
        * maintaining.texi (Create Tags Table): Add text about the dangers of

diff --git a/man/maintaining.texi b/man/maintaining.texi
index ab98dccd350b7256bb8e4fd6acb6d16ded1e5047..c9e77ede2a135215f67fe4bd7810291ad7bb0573 100644 (file)
--- a/man/maintaining.texi
+++ b/man/maintaining.texi
@@ -409,10 +409,10 @@ source files, and the tags file will still refer correctly to the source
 files.  If the tags file is in @file{/dev}, however, the file names are
 made relative to the current working directory.  This is useful, for
 example, when writing the tags to @file{/dev/stdout}.
-
-  Notice that, in the usual case of using relative file names, you
-should not use a symbolic link pointing to a tags file in a different
-directory, because this would generally render the file names invalid.
+ 
+  When using a a relative file name, it should not be a symbolic link
+pointing to a tags file in a different directory, because this would
+generally render the file names invalid.
 
   If you specify absolute file names as arguments to @code{etags}, then
 the tags file will contain absolute file names.  This way, the tags file