* doc/c-tree.texi (Tree overview): Fix typos.

From-SVN: r58640

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index edd8a7eb2478aa8fa1f3be26c98652275456bc07..6250ccd56dcee239e9cb38fddf458926ce2e1d97 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2002-10-28  Andreas Bauer  <baueran@in.tum.de>
+
+       * doc/c-tree.texi (Tree overview): Fix typos.
+
 2002-10-29  Phil Edwards  <pme@gcc.gnu.org>
 
        * Makefile.in (gnucompare*):  Only record bad comparisons

diff --git a/gcc/doc/c-tree.texi b/gcc/doc/c-tree.texi
index 0b9f4d69d75e345ac385df7cc08e8d96197322ef..8f5a5bb74d23c7f8661c410a59c0b16685b03c44 100644 (file)
--- a/gcc/doc/c-tree.texi
+++ b/gcc/doc/c-tree.texi
@@ -84,8 +84,8 @@ we will refer to trees in ordinary type, rather than in @code{this
 font}, except when talking about the actual C type @code{tree}.
 
 You can tell what kind of node a particular tree is by using the
-@code{TREE_CODE} macro.  Many, many macros take a trees as input and
-return trees as output.  However, most macros require a certain kinds of
+@code{TREE_CODE} macro.  Many, many macros take trees as input and
+return trees as output.  However, most macros require a certain kind of
 tree node as input.  In other words, there is a type-system for trees,
 but it is not reflected in the C type-system.