diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2016-09-15 20:21:15 +0200 |
|---|---|---|
| committer | NIIBE Yutaka <gniibe@fsij.org> | 2016-09-17 09:00:37 +0200 |
| commit | 0d67241e317b172a258a910c02d90639e2b08fce (patch) | |
| tree | f1f68c8a94af20f1a3273da46633c7f8af750bc4 /doc/Notes | |
| parent | move some file encodings to UTF-8 (diff) | |
| download | gnupg2-0d67241e317b172a258a910c02d90639e2b08fce.tar.xz gnupg2-0d67241e317b172a258a910c02d90639e2b08fce.zip | |
Fix more spelling
* NEWS, acinclude.m4, agent/command-ssh.c, agent/command.c,
agent/gpg-agent.c, agent/keyformat.txt, agent/protect-tool.c,
common/asshelp.c, common/b64enc.c, common/recsel.c, doc/DETAILS,
doc/HACKING, doc/Notes, doc/TRANSLATE, doc/dirmngr.texi,
doc/faq.org, doc/gpg-agent.texi, doc/gpg.texi, doc/gpgsm.texi,
doc/instguide.texi, g10/armor.c, g10/gpg.c, g10/keyedit.c,
g10/mainproc.c, g10/pkclist.c, g10/tofu.c, g13/sh-cmd.c,
g13/sh-dmcrypt.c, kbx/keybox-init.c, m4/pkg.m4, sm/call-dirmngr.c,
sm/gpgsm.c, tests/Makefile.am, tests/gpgscm/Manual.txt,
tests/gpgscm/scheme.c, tests/openpgp/gpgv-forged-keyring.scm,
tests/openpgp/multisig.test, tests/openpgp/verify.scm,
tests/pkits/README, tools/applygnupgdefaults,
tools/gpg-connect-agent.c, tools/mime-maker.c, tools/mime-parser.c:
minor spelling cleanup.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Diffstat (limited to 'doc/Notes')
| -rw-r--r-- | doc/Notes | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -7,7 +7,7 @@ There are two ways: 1. Let gpg-agent do this for you. Since version 1.9.9 you need to add the option --allow-mark-trusted gpg-agent.conf or when - invoking gpg-agent. Everytime gpgsm notices an untrusted root + invoking gpg-agent. Every time gpgsm notices an untrusted root certificate gpg-agent will pop up a dialog to ask whether this certificate should be trusted. This is similar to whatmost browsers do. @@ -22,7 +22,7 @@ There are two ways: the fingerprints of the trusted root certificates. There are comments on the top explaining the simple format. The current CVS version allows for colons in the fingerprint, so you can - easily cut and paste it from whereever you know that this is the + easily cut and paste it from wherever you know that this is the correct fingerprint. An example for an entry in the trustlist.txt is: @@ -199,12 +199,12 @@ dirmngr libgcrypt libksba libassuan [statically linked] - libldap [system libary] - liblber [system libary] - libsasl [system libary, required by libldap] - libdb2 [system libary, required by libsasl] - libcrypt [system libary, required by libsasl - OOPS] - libpam [system libary, required by libsasl] + libldap [system library] + liblber [system library] + libsasl [system library, required by libldap] + libdb2 [system library, required by libsasl] + libcrypt [system library, required by libsasl - OOPS] + libpam [system library, required by libsasl] [Standard system libraries] pinentry-curses |