[enh] enhance Readme.rst and a doctring

README.rst

@@ -65,7 +65,7 @@ Development
 
     make check
 
-* Run all unit tests with::
+* Run all unit tests (builtin module unittest) with::
 
     make tests
 
@@ -76,6 +76,8 @@ Development
 Documentation
 -------------
 
+When writing docstrings, use the rst format recommended by https://www.python.org/dev/peps/pep-0287/#docstring-significant-features
+
 * Install Sphinx::
 
     pip install -r requirements_dev.txt
@@ -85,7 +87,7 @@ Documentation
     make docs
 
 * HTML Documentation is generated in docs/_build/html folder.
-* `Examples <https://git.duniter.org/clients/python/duniterpy/tree/master/examples>`_
+* `Examples are more fun than a TLTR doc <https://git.duniter.org/clients/python/duniterpy/tree/master/examples>`_
 
 Packaging and deploy
 --------------------

duniterpy/key/ascii_armor.py

@@ -235,22 +235,18 @@ class AsciiArmor:
     def parse(ascii_armor_message: str, signing_key: Optional[SigningKey] = None,
               sender_pubkeys: Optional[List[str]] = None) -> dict:
         """
-        Return a dict with parsed content (decrypted message, signature validation)
+        Return a dict with parsed content (decrypted message, signature validation) ::
 
             {
-                'message':
-                    {
-                        'fields': {},
-                        'content': str,
-
-                     },
-
-                'signatures': [
-                    {'pubkey': str, 'valid': bool, fields: {}}
-
-                ]
-
-            }
+               'message':
+                   {
+                       'fields': {},
+                       'content': str,
+                    },
+               'signatures': [
+                   {'pubkey': str, 'valid': bool, fields: {}}
+               ]
+           }
 
         :param ascii_armor_message: The Ascii Armor Message Block including BEGIN and END headers
         :param signing_key: Optional Libnacl SigningKey instance to decrypt message