aboutsummaryrefslogtreecommitdiffstats
path: root/g10/getkey.c
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <[email protected]>2018-10-24 19:56:18 +0000
committerDaniel Kahn Gillmor <[email protected]>2018-10-24 19:56:18 +0000
commit54eb375ff14e2a93cea70eab35719be4d25f51ca (patch)
tree99a6159cfc9cc26696ddd5c842095fd046cb8d6e /g10/getkey.c
parentdoc: fix spelling mistakes (diff)
downloadgnupg-54eb375ff14e2a93cea70eab35719be4d25f51ca.tar.gz
gnupg-54eb375ff14e2a93cea70eab35719be4d25f51ca.zip
all: fix spelling and typos
Signed-off-by: Daniel Kahn Gillmor <[email protected]>
Diffstat (limited to 'g10/getkey.c')
-rw-r--r--g10/getkey.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/g10/getkey.c b/g10/getkey.c
index ea2dee21d..75ce9cb38 100644
--- a/g10/getkey.c
+++ b/g10/getkey.c
@@ -60,7 +60,7 @@ struct getkey_ctx_s
search or not. A search that is exact requires that a key or
subkey meet all of the specified criteria. A search that is not
exact allows selecting a different key or subkey from the
- keyblock that matched the critera. Further, an exact search
+ keyblock that matched the criteria. Further, an exact search
returns the key or subkey that matched whereas a non-exact search
typically returns the primary key. See finish_lookup for
details. */
@@ -3364,7 +3364,7 @@ merge_selfsigs (ctrl_t ctrl, kbnode_t keyblock)
*
* 1. No requested usage and no primary key requested
* Examples for this case are that we have a keyID to be used
- * for decrytion or verification.
+ * for decryption or verification.
* 2. No usage but primary key requested
* This is the case for all functions which work on an
* entire keyblock, e.g. for editing or listing