1 files changed, 8 insertions, 4 deletions

diff --git a/39.md b/39.md
index cc3f796..b84603c 100644
--- a/39.md
+++ b/39.md
@@ -39,24 +39,28 @@ Identity names SHOULD be normalized if possible by replacing uppercase letters w
 
 ### `github`
 
-Identity: A GitHub username.  
+Identity: A GitHub username.
+
 Proof: A GitHub Gist ID. This Gist should be created by `<identity>` with a single file that has the text `Verifying that I control the following Nostr public key: <npub encoded public key>`.  
 This can be located at `https://gist.github.com/<identity>/<proof>`.
 
 ### `twitter`
 
-Identity: A Twitter username.  
+Identity: A Twitter username.
+
 Proof: A Tweet ID. The tweet should be posted by `<identity>` and have the text `Verifying my account on nostr My Public Key: "<npub encoded public key>"`.  
 This can be located at `https://twitter.com/<identity>/status/<proof>`.
 
 ### `mastodon`
 
 Identity: A Mastodon instance and username in the format `<instance>/@<username>`.
-Proof: A Mastodon post ID. This post should be published by `<username>@<instance>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`.  
+
+Proof: A Mastodon post ID. This post should be published by `<username>@<instance>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`.
 This can be located at `https://<identity>/<proof>`.
 
 ### `telegram`
 
 Identity: A Telegram user ID.
+
 Proof: A string in the format `<ref>/<id>` which points to a message published in the public channel or group with name `<ref>` and message ID `<id>`. This message should be sent by user ID `<identity>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`.  
-This can be located at `https://t.me/<proof>`.
\ No newline at end of file
+This can be located at `https://t.me/<proof>`.