diff --git a/content/posts/slixmpp-omemo-release.md b/content/posts/slixmpp-omemo-release.md
index 5f0385d..d92976e 100644
--- a/content/posts/slixmpp-omemo-release.md
+++ b/content/posts/slixmpp-omemo-release.md
@@ -53,7 +53,7 @@ port of the original library implemented in Signal.
 The only bits that prevent him for releasing his library under MIT is the
 wireformat, that has to be the same as the original implementation as
 specified in [XEP-0384][OMEMO]. Providing that we define another wireformat
-for all OMEMO implementations to use, this restriction will go away, (still
+for all OMEMO implementations to use, this restriction will go away (still
 easier said than done.)
 
 [python-axolotl]: https://pypi.org/project/python-axolotl/
@@ -64,9 +64,9 @@ easier said than done.)
 There is still lots of things to be improved in OMEMO, the specification.
 
 I would personally like to see what is usually called _Full Stanza
-Encryption_, (it's really only partial). Today, an OMEMO implementation will
+Encryption_ (it's really only partial). Today, an OMEMO implementation will
 only encrypt the plaintext part of messages you send, and either leak
-everything else, (e.g., chatstates, receipts, corrections, xhtml-im), or
+everything else (e.g., chatstates, receipts, corrections, xhtml-im), or
 effectively disable them, for privacy-conscious implementations.
 
 I would also like to drop _Forward Secrecy_, in the context of Instant