[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may'
From: |
Richard Stallman |
Subject: |
bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may' |
Date: |
Thu, 05 Jul 2012 06:13:56 -0400 |
The keyword @code{&rest} (which must be followed by a single
-argument name) indicates that any number of arguments can follow. The
+argument name) indicates that any number of arguments may follow.
The old text is correct. Replacing it with "may" is not wrong, but it
adds a formality that we try to avoid in GNU manuals.
So please don't make this change.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call
- bug#11862: [PATCH 0/9] doc/lispref/intro.texi: Copyediting, Michael Witten, 2012/07/04
- bug#11862: [PATCH 1/9] doc/lispref/intro.texi: Offset modifier with a comma, Michael Witten, 2012/07/04
- bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may', Michael Witten, 2012/07/04
- bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may',
Richard Stallman <=
- bug#11862: [PATCH 7/9] doc/lispref/intro.texi: `optional' -> `&optional';, Michael Witten, 2012/07/04
- bug#11862: [PATCH 5/9] doc/lispref/intro.texi: Use singular form in a sentence, Michael Witten, 2012/07/04
- bug#11862: [PATCH 4/9] doc/lispref/intro.texi: More precise language, Michael Witten, 2012/07/04
- bug#11862: [PATCH 3/9] doc/lispref/intro.texi: Eradicate that pesky future tense, Michael Witten, 2012/07/04
- bug#11862: [PATCH 8/9] doc/lispref/intro.texi: More precise language for, Michael Witten, 2012/07/04