summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2006-08-16 12:47:53 +0200
committerWerner Koch <wk@gnupg.org>2006-08-16 12:47:53 +0200
commitb744f963d7061ce55d2eed65b281298476e54fb7 (patch)
tree6e8ccb3c39a45c16b4ca6cdb2273eb3b8bc2a888 /doc
parentChanged HTTP API. (diff)
downloadgnupg2-b744f963d7061ce55d2eed65b281298476e54fb7.tar.xz
gnupg2-b744f963d7061ce55d2eed65b281298476e54fb7.zip
With --enable-gpg the keyservers are now build and a first test using gpg2
shows no prblems. Needs more testing of course.
Diffstat (limited to 'doc')
-rw-r--r--doc/gpg-agent.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/gpg-agent.texi b/doc/gpg-agent.texi
index 39b79d306..e4022bb8e 100644
--- a/doc/gpg-agent.texi
+++ b/doc/gpg-agent.texi
@@ -430,7 +430,7 @@ agent. By default they may all be found in the current home directory
hash mark, as well as empty lines are ignored. To mark a key as trusted
you need to enter its fingerprint followed by a space and a capital
letter @code{S}. Colons may optionally be used to separate the bytes of
- a fingerprint; this allows to cut and paste the fingeperint from a key
+ a fingerprint; this allows to cut and paste the fingerprint from a key
listing output.
Here is an example where two keys are marked as ultimately trusted: