diff options
| author | Jeff Law <law@gcc.gnu.org> | 1998-05-06 15:09:07 -0600 |
|---|---|---|
| committer | Jeff Law <law@gcc.gnu.org> | 1998-05-06 15:09:07 -0600 |
| commit | 38e012594edc0e7783e3e6d91960c91469df4164 (patch) | |
| tree | e5214fcd8a05d4b329467434fcdea16f33d3ce7b /etc | |
| parent | f103890ba552cf55c0aa79d35968db46785a94d0 (diff) | |
| download | gcc-38e012594edc0e7783e3e6d91960c91469df4164.zip gcc-38e012594edc0e7783e3e6d91960c91469df4164.tar.gz gcc-38e012594edc0e7783e3e6d91960c91469df4164.tar.bz2 | |
typo typo fixes fixes
From-SVN: r19601
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/make-stds.texi | 4 | ||||
| -rw-r--r-- | etc/standards.texi | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/etc/make-stds.texi b/etc/make-stds.texi index e7c9cf9..7f04129 100644 --- a/etc/make-stds.texi +++ b/etc/make-stds.texi @@ -79,7 +79,7 @@ foo.1 : foo.man sedscript @noindent will fail when the build directory is not the source directory, because -@file{foo.man} and @file{sedscript} are in the the source directory. +@file{foo.man} and @file{sedscript} are in the source directory. When using GNU @code{make}, relying on @samp{VPATH} to find the source file will work in the case where there is a single dependency file, @@ -724,7 +724,7 @@ The easiest way to do this is to create a subdirectory appropriately named, use @code{ln} or @code{cp} to install the proper files in it, and then @code{tar} that subdirectory. -Compress the tar file file with @code{gzip}. For example, the actual +Compress the tar file with @code{gzip}. For example, the actual distribution file for GCC version 1.40 is called @file{gcc-1.40.tar.gz}. The @code{dist} target should explicitly depend on all non-source files diff --git a/etc/standards.texi b/etc/standards.texi index 4170093..ff0d88b 100644 --- a/etc/standards.texi +++ b/etc/standards.texi @@ -2570,7 +2570,7 @@ also contain this information. If the manual is changing more frequently than or independent of the program, also state a version number for the manual in both of these places. -Each program documented in the manual should should have a node named +Each program documented in the manual should have a node named @samp{@var{program} Invocation} or @samp{Invoking @var{program}}. This node (together with its subnodes, if any) should describe the program's command line arguments and how to run it (the sort of information people |