From 91eb242d635f6650bcc7d8d82a5bfd142222bd5a Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Fri, 17 Nov 2017 10:17:08 +0800 Subject: [PATCH] doc: clarify that --encrypt refers to public key encryption -- A simple read of gpg(1) is ambiguous about whether --encrypt could be for either symmetric or pubkey encryption. Closer inference suggests that --encrypt is about pubkey encryption only. Make that clearer on a first read. Signed-off-by: Daniel Kahn Gillmor --- doc/gpg.texi | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/gpg.texi b/doc/gpg.texi index bd45b0422..35bb9a810 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -196,11 +196,13 @@ Make a detached signature. @item --encrypt @itemx -e @opindex encrypt -Encrypt data. This command may be combined with @option{--sign} (to -sign and encrypt a message), @option{--symmetric} (to encrypt a -message that can decrypted using a secret key or a passphrase), or -@option{--sign} and @option{--symmetric} together (for a signed -message that can be decrypted using a secret key or a passphrase). +Encrypt data to one or more public keys. This command may be combined +with @option{--sign} (to sign and encrypt a message), +@option{--symmetric} (to encrypt a message that can decrypted using a +secret key or a passphrase), or @option{--sign} and +@option{--symmetric} together (for a signed message that can be +decrypted using a secret key or a passphrase). @option{--recipient} +and related options specify which public keys to use for encryption. @item --symmetric @itemx -c