[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] Fix doc typos.

From: Jim Meyering
Subject: [PATCH] Fix doc typos.
Date: Sat, 08 Mar 2008 22:04:59 +0100

Hi James,

Here's a fix for two doc typos.

 ChangeLog           |    6 ++++++
 doc/find-maint.texi |    6 +++---
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index cdae6bf..7dcd73f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2008-03-08  Jim Meyering  <address@hidden>
+       Fix doc typos.
+       * doc/find-maint.texi (Security): s/ongest/longest/
+       (Making Releases): s/the the/the/
 2008-02-15  Eric Blake  <address@hidden>

        Avoid compiler warnings.
diff --git a/doc/find-maint.texi b/doc/find-maint.texi
index 917f58c..49be265 100644
--- a/doc/find-maint.texi
+++ b/doc/find-maint.texi
@@ -23,7 +23,7 @@ be made and tested, and what resources exist to help 

 This is edition @value{EDITION}, for findutils version @value{VERSION}.

-Copyright @copyright{} 2007 Free Software Foundation, Inc.
+Copyright @copyright{} 2007, 2008 Free Software Foundation, Inc.

 Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.2
@@ -852,7 +852,7 @@ All existing releases of findutils are affected.

-To discover the ongest path name on a given system, you can use the
+To discover the longest path name on a given system, you can use the
 following command (requires GNU findutils and GNU coreutils):

@@ -1125,7 +1125,7 @@ and @file{NEWS} files to advance the release numbers.   
For example,
 if you have just released @samp{4.6.2}, bump the release number to
 @samp{4.6.3-CVS}.  The point of the @samp{-CVS} suffix here is that a
 findutils binary built from CVS will bear a release number indicating
-it's not built from the the ``official'' source release.
+it's not built from the ``official'' source release.
 @item Close bugs; any bugs recorded on Savannah which were fixed in this
 release should now be marked as closed.   Update the @samp{Fixed
 Release} field of these bugs appropriately and make sure the

reply via email to

[Prev in Thread] Current Thread [Next in Thread]