[PATCH] doc: clarify that --encrypt refers to public key encryption

[Daniel Kahn Gillmor]

* doc/gpg.texi: update --encrypt stanza

--

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 <dkg at fifthhorseman.net>
---
 doc/gpg.texi | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/gpg.texi b/doc/gpg.texi
index bd45b0422..858105d27 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -196,11 +196,12 @@ 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
- at option{--sign} and @option{--symmetric} together (for a signed
-message that can be decrypted using a secret key or a passphrase).
+Encrypt data to a public key. This command may be combined with
+ at 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).
 
 @item --symmetric
 @itemx -c
-- 
2.15.0