[patch] GNU CC -> GCC in doc/

[Nathanael Nerode <neroden at twcny dot rr dot com>]

I'd like review for this one to make sure I got the sense right in
headerdirs.texi.

	* collect2.texi: GNU CC -> GCC.
	* headerdirs.texi: GNU CC -> GCC or GNU C.

Index: collect2.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/collect2.texi,v
retrieving revision 1.2
diff -u -r1.2 collect2.texi
--- collect2.texi	24 Jan 2003 15:57:41 -0000	1.2
+++ collect2.texi	13 Mar 2003 02:48:44 -0000
@@ -5,7 +5,7 @@
 @node Collect2
 @chapter @code{collect2}
 
-GNU CC uses a utility called @code{collect2} on nearly all systems to arrange
+GCC uses a utility called @code{collect2} on nearly all systems to arrange
 to call various initialization functions at start time.
 
 The program @code{collect2} works by linking the program once and
Index: headerdirs.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/headerdirs.texi,v
retrieving revision 1.2
diff -u -r1.2 headerdirs.texi
--- headerdirs.texi	24 Jan 2003 15:57:41 -0000	1.2
+++ headerdirs.texi	13 Mar 2003 02:48:44 -0000
@@ -6,28 +6,28 @@
 @chapter Standard Header File Directories
 
 @code{GCC_INCLUDE_DIR} means the same thing for native and cross.  It is
-where GNU CC stores its private include files, and also where GNU CC
-stores the fixed include files.  A cross compiled GNU CC runs
+where GCC stores its private include files, and also where GCC
+stores the fixed include files.  A cross compiled GCC runs
 @code{fixincludes} on the header files in @file{$(tooldir)/include}.
 (If the cross compilation header files need to be fixed, they must be
-installed before GNU CC is built.  If the cross compilation header files
-are already suitable for ISO C and GNU CC, nothing special need be
+installed before GCC is built.  If the cross compilation header files
+are already suitable for ISO C and GNU C, nothing special need be
 done).
 
 @code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross.  It
 is where @command{g++} looks first for header files.  The C++ library
 installs only target independent header files in that directory.
 
- at code{LOCAL_INCLUDE_DIR} is used only by native compilers.  GNU CC
+ at code{LOCAL_INCLUDE_DIR} is used only by native compilers.  GCC
 doesn't install anything there.  It is normally
 @file{/usr/local/include}.  This is where local additions to a packaged
 system should place header files.
 
- at code{CROSS_INCLUDE_DIR} is used only by cross compilers.  GNU CC
+ at code{CROSS_INCLUDE_DIR} is used only by cross compilers.  GCC
 doesn't install anything there.
 
 @code{TOOL_INCLUDE_DIR} is used for both native and cross compilers.  It
-is the place for other packages to install header files that GNU CC will
+is the place for other packages to install header files that GCC will
 use.  For a cross-compiler, this is the equivalent of
 @file{/usr/include}.  When you build a cross-compiler,
 @code{fixincludes} processes any header files in this directory.