summaryrefslogtreecommitdiffstats
path: root/doc/whats-new-in-2.1.txt
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2016-08-02 04:19:17 +0200
committerJustus Winter <justus@g10code.com>2016-08-03 16:55:33 +0200
commitdc107b78509807db375d3a382eb3376cd2183357 (patch)
treeef7301b4b8d2556a526e0f3c79cd532ba98f6c60 /doc/whats-new-in-2.1.txt
parentdirmngr: Emit correct spelling of "superseded". (diff)
downloadgnupg2-dc107b78509807db375d3a382eb3376cd2183357.tar.xz
gnupg2-dc107b78509807db375d3a382eb3376cd2183357.zip
More cleanup of "allow to".
* README, agent/command.c, agent/keyformat.txt, common/i18n.c, common/iobuf.c, common/keyserver.h, dirmngr/cdblib.c, dirmngr/ldap-wrapper.c, doc/DETAILS, doc/TRANSLATE, doc/announce-2.1.txt, doc/gpg.texi, doc/gpgsm.texi, doc/scdaemon.texi, doc/tools.texi, doc/whats-new-in-2.1.txt, g10/export.c, g10/getkey.c, g10/import.c, g10/keyedit.c, m4/ksba.m4, m4/libgcrypt.m4, m4/ntbtls.m4, po/ca.po, po/cs.po, po/da.po, po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/fi.po, po/fr.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po, po/nb.po, po/pl.po, po/pt.po, po/ro.po, po/ru.po, po/sk.po, po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po, scd/app-p15.c, scd/ccid-driver.c, scd/command.c, sm/gpgsm.c, sm/sign.c, tools/gpgconf-comp.c, tools/gpgtar.h: replace "Allow to" with clearer text. In standard English, the normal construction is "${XXX} allows ${YYY} to" -- that is, the subject (${XXX}) of the sentence is allowing the object (${YYY}) to do something. When the object is missing, the phrasing sounds awkward, even if the object is implied by context. There's almost always a better construction that isn't as awkward. These changes should make the language a bit clearer. Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Diffstat (limited to 'doc/whats-new-in-2.1.txt')
-rw-r--r--doc/whats-new-in-2.1.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/whats-new-in-2.1.txt b/doc/whats-new-in-2.1.txt
index dd29c669b..19ed8b9fc 100644
--- a/doc/whats-new-in-2.1.txt
+++ b/doc/whats-new-in-2.1.txt
@@ -540,7 +540,7 @@ https://gnupg.org/faq/whats-new-in-2.1.html
key id matching the key id of another key. Importing a key with a
long key id already used by another key in gpg’s local key store was
not possible due to checks done on import. Now, if the “wrong” key
- has been imported first /gpg/ would not allow to later import the
+ has been imported first /gpg/ would not allow later import of the
second “correct” key. This problem has been fixed in 2.1 by allowing
the import and by doing trial verification against all matching keys.