Re: typos in the manual

[Alexandre Duret-Lutz]

>>> "Stepan" == Stepan Kasal <address@hidden> writes:

 Stepan> I have noticed two typos in the manual, see the attached patch.

Thanks, I'm checking this in.

2004-12-05  Stepan Kasal  <address@hidden>

        * doc/automake.texi (renamed objects, CVS): Typos.

Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.44.2.21
diff -u -r1.44.2.21 automake.texi
--- doc/automake.texi   5 Dec 2004 13:06:03 -0000       1.44.2.21
+++ doc/automake.texi   5 Dec 2004 13:09:36 -0000
@@ -7389,7 +7389,7 @@
 update, not the original timestamp of this revision.  This is meant to
 make sure that @command{make} notices sources files have been updated.
 
-This times tamp shift is troublesome when both sources and generated
+This timestamp shift is troublesome when both sources and generated
 files are kept under CVS.  Because CVS processes files in alphabetical
 order, @file{configure.ac} will appear older than @file{configure}
 after a @command{cvs update} that updates both files, even if
@@ -8056,12 +8056,12 @@
 @noindent
 Obviously the two programs are built from the same source, but it
 would be bad if they shared the same object, because @file{generic.o}
-cannot be built with both @code{-DEXIT_CODE=0} *and*
+cannot be built with both @code{-DEXIT_CODE=0} @emph{and}
 @code{-DEXIT_CODE=1}.  Therefore @command{automake} outputs rules to
 build two different objects: @file{true-generic.o} and
 @file{false-generic.o}.
 
address@hidden doesn't actually look whether sources files are
address@hidden doesn't actually look whether source files are
 shared to decide if it must rename objects.  It will just rename all
 objects of a target as soon as it sees per-target compilation flags
 are used.

-- 
Alexandre Duret-Lutz