python: documentation fixes

* Typographic and whitespace error correction pertaining to the
  previous update.

Signed-off-by: Ben McGinnes <[email protected]>

4 files changed, 9 insertions, 3 deletions

diff --git a/lang/python/doc/rst/maintenance-mode.rst b/lang/python/doc/rst/maintenance-mode.rst
index 75cd947a..bbd25211 100644
--- a/lang/python/doc/rst/maintenance-mode.rst
+++ b/lang/python/doc/rst/maintenance-mode.rst
@@ -78,6 +78,9 @@ decryption, verification, validation, trust levels and so on.
 Any wanted features lacking in the Python bindings are usually lacking
 because they are missing from GPGME itself (e.g. revoking keys via the
 API) and in such cases they are usually deliberately excluded. More
+discussion of these issues can be found in the archives of the
+`gnupg-devel mailing
+list <https://lists.gnupg.org/mailman/listinfo/gnupg-devel>`__.
 
 Any features existing in the dynamically generated layer for which
 people want a specific, higher level function included to make it more
diff --git a/lang/python/doc/src/gpgme-python-howto b/lang/python/doc/src/gpgme-python-howto
index fe1fc2b4..43d0c2b3 100644
--- a/lang/python/doc/src/gpgme-python-howto
+++ b/lang/python/doc/src/gpgme-python-howto
@@ -21,7 +21,6 @@
 | Author GPG Key: | [[https://hkps.pool.sks-keyservers.net/pks/lookup?search=0xDB4724E6FA4286C92B4E55C4321E4E2373590E5D&exact=on&op=get][DB4724E6FA4286C92B4E55C4321E4E2373590E5D]] |
 | Language:       | Australian English, British English      |
 | Language codes: | en-AU, en-GB, en                         |
-#+TBLFM: 
 
 This document provides basic instruction in how to use the GPGME
 Python bindings to programmatically leverage the GPGME library.
diff --git a/lang/python/doc/src/maintenance-mode b/lang/python/doc/src/maintenance-mode
index ef56e4e6..e7a8f282 100644
--- a/lang/python/doc/src/maintenance-mode
+++ b/lang/python/doc/src/maintenance-mode
@@ -76,7 +76,9 @@ decryption, verification, validation, trust levels and so on.
 
 Any wanted features lacking in the Python bindings are usually lacking
 because they are missing from GPGME itself (e.g. revoking keys via the
-API) and in such cases they are usually deliberately excluded.  More 
+API) and in such cases they are usually deliberately excluded.  More
+discussion of these issues can be found in the archives of the
+[[https://lists.gnupg.org/mailman/listinfo/gnupg-devel][gnupg-devel mailing list]].
 
 Any features existing in the dynamically generated layer for which
 people want a specific, higher level function included to make it more
diff --git a/lang/python/doc/texinfo/maintenance-mode.texi b/lang/python/doc/texinfo/maintenance-mode.texi
index ad526068..a60236fe 100644
--- a/lang/python/doc/texinfo/maintenance-mode.texi
+++ b/lang/python/doc/texinfo/maintenance-mode.texi
@@ -104,7 +104,9 @@ decryption, verification, validation, trust levels and so on.
 
 Any wanted features lacking in the Python bindings are usually lacking
 because they are missing from GPGME itself (e.g. revoking keys via the
-API) and in such cases they are usually deliberately excluded.  More 
+API) and in such cases they are usually deliberately excluded.  More
+discussion of these issues can be found in the archives of the
+@uref{https://lists.gnupg.org/mailman/listinfo/gnupg-devel, gnupg-devel mailing list}.
 
 Any features existing in the dynamically generated layer for which
 people want a specific, higher level function included to make it more