aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBen McGinnes <[email protected]>2018-05-15 04:46:11 +0000
committerBen McGinnes <[email protected]>2018-05-15 04:46:11 +0000
commitaa4875bd06f151bde74972b2dd4220b32a34f39e (patch)
tree22eca3866c361b92399892766e334cea0a9ea9aa
parentdocs: python bindings howto (diff)
downloadgpgme-aa4875bd06f151bde74972b2dd4220b32a34f39e.tar.gz
gpgme-aa4875bd06f151bde74972b2dd4220b32a34f39e.zip
docs: python howto DITA
* Corrected a minor markup typo.
-rw-r--r--lang/python/docs/dita/howto/part04/encrypt-to-many.dita2
1 files changed, 1 insertions, 1 deletions
diff --git a/lang/python/docs/dita/howto/part04/encrypt-to-many.dita b/lang/python/docs/dita/howto/part04/encrypt-to-many.dita
index 34c18b40..9afbc653 100644
--- a/lang/python/docs/dita/howto/part04/encrypt-to-many.dita
+++ b/lang/python/docs/dita/howto/part04/encrypt-to-many.dita
@@ -7,7 +7,7 @@
<p>Encrypting to multiple keys essentially just expands upon the key selection process
and the recipients from the previous examples.</p>
<p>The following example encrypts a message (<codeph>text</codeph>) to everyone with an email
- address on the <codeph>gnupg.org </codeph>domain,<fn>You probably don't really want to do
+ address on the <codeph>gnupg.org</codeph> domain,<fn>You probably don't really want to do
this. Searching the keyservers for "gnupg.org" produces over 400 results, the majority of
which aren't actually at the gnupg.org domain, but just included a comment regarding the
project in their key somewhere.</fn> but does <i>not</i> encrypt to a default key or other