summaryrefslogtreecommitdiff
path: root/docs/source
diff options
context:
space:
mode:
authorPatrick Totzke <patricktotzke@gmail.com>2015-12-16 15:46:56 +0000
committerPatrick Totzke <patricktotzke@gmail.com>2015-12-16 15:46:56 +0000
commit668465c4bea2782d352ab88ba983c6615e94a9a1 (patch)
treeca1d0036a6ff2bd217e94051ff777c29db822d8d /docs/source
parent1c3c961dcc6db15b460c1b62623caa59c1e9cece (diff)
polish docs
Diffstat (limited to 'docs/source')
-rw-r--r--docs/source/usage/crypto.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/source/usage/crypto.rst b/docs/source/usage/crypto.rst
index 243cc445..03e1dc2e 100644
--- a/docs/source/usage/crypto.rst
+++ b/docs/source/usage/crypto.rst
@@ -40,8 +40,9 @@ in envelope mode to ask alot to encrypt the mail before sending.
The :ref:`encrypt <cmd.envelope.encrypt>` command accepts an optional
hint string as argument to determine the key of the recipient.
-If you want to access encrypt mail later it is useful to add yourself to the
-list of recipients when encrypting with gpg (not the recipients whom mail is
-actually send to). The simplest way to do this is to use the `encrypt-to`
-option in the :file:`~/.gnupg/gpg.conf`. But you might have to specify the
-correct encryption subkey otherwise gpg seems to throw an error.
+.. note::
+ If you want to access encrypt mail later it is useful to add yourself to the
+ list of recipients when encrypting with gpg (not the recipients whom mail is
+ actually send to). The simplest way to do this is to use the `encrypt-to`
+ option in the :file:`~/.gnupg/gpg.conf`. But you might have to specify the
+ correct encryption subkey otherwise gpg seems to throw an error.