gnustandards-commit
[Top][All Lists]
Advanced

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

gnustandards standards.texi


From: Karl Berry
Subject: gnustandards standards.texi
Date: Tue, 16 Jan 2018 18:48:07 -0500 (EST)

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       18/01/16 18:48:07

Modified files:
        .              : standards.texi 

Log message:
        typos

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.254&r2=1.255

Patches:
Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.254
retrieving revision 1.255
diff -u -b -r1.254 -r1.255
--- standards.texi      15 Jan 2018 23:28:02 -0000      1.254
+++ standards.texi      16 Jan 2018 23:48:07 -0000      1.255
@@ -28,7 +28,7 @@
 
 Copyright @copyright{} 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-2011, 2012, 2013, 2014, 2015, 2016 Free Software Foundation, Inc.
+2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018 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.3 or
@@ -3565,7 +3565,7 @@
 of the overall change.  This should be as long as needed to give
 a clear description.
 
-The give a list of names of the entities or definitions that you
+Then give a list of names of the entities or definitions that you
 changed, according to the files they are in, and what was changed
 in each one.  @xref{Style of Change Logs}.
 
@@ -3695,7 +3695,7 @@
 files (manuals, help files, media files, etc.).  This is because they
 are not susceptible to bugs that are hard to understand.  To correct
 an error, you need not know the history of the erroneous passage; it
-is enough to compare what the file says with the the actual facts.
+is enough to compare what the file says with the actual facts.
 
 However, you should keep change logs for non-software files when the
 project gets copyright assignments from its contributors, so as to



reply via email to

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