summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2009-04-25 07:22:50 +0000
committerEli Zaretskii <eliz@gnu.org>2009-04-25 07:22:50 +0000
commit4bf0ac18dbbcf5dbcc01a0d0c7ee118e75aaf782 (patch)
tree96c823134e8bbb5db34178f8d92f9325bab48a9c /doc
parentb207de6bed27017c245e15118145ae1da53c11de (diff)
downloademacs-4bf0ac18dbbcf5dbcc01a0d0c7ee118e75aaf782.tar.gz
(Tags): Fix last change.
Diffstat (limited to 'doc')
-rw-r--r--doc/emacs/maintaining.texi9
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/emacs/maintaining.texi b/doc/emacs/maintaining.texi
index 13fdb123135..4a5afac6523 100644
--- a/doc/emacs/maintaining.texi
+++ b/doc/emacs/maintaining.texi
@@ -1496,11 +1496,10 @@ conventional name for a tags table file is @file{TAGS}.
Each entry in the tags table records the name of a tag, the name of
the file that the tag is defined in (implicitly), and the position in
that file of the tag's definition. If the file is a generated file,
-the tags for the generated file reference the originating source file.
-Examples of generated files include C files generated from Cweb source
-files or from a Yacc parser or Lex scanner definitions, @file{.i}
-preprocessed C files, and Fortran files produced by preprocessing
-@file{.fpp} source files.
+its tags reference the originating source file. Examples of generated
+files include C files generated from Cweb source files or from a Yacc
+parser or Lex scanner definitions, @file{.i} preprocessed C files, and
+Fortran files produced by preprocessing @file{.fpp} source files.
Just what names from the described files are recorded in the tags table
depends on the programming language of the described file. They