diff --git a/content/posts/e2ee/index.md b/content/posts/e2ee/index.md
index 0ca237e..d224459 100644
--- a/content/posts/e2ee/index.md
+++ b/content/posts/e2ee/index.md
@@ -26,13 +26,8 @@ For a more in-depth look at these various considerations, we recommend [The Guid
The following options for encrypted messaging are listed from most metadata protection to least.
-TLDR: Use Cwtch. Don't use Signal or PGP.
+**TLDR: Use Cwtch. Don't use Signal or PGP.**
-
-
-
# Cwtch
@@ -46,6 +41,16 @@ TLDR: Use Cwtch. Don't use Signal or PGP.
Cwtch is our preference, by a long shot. It is currently transitioning from [beta to stable versions](https://docs.cwtch.im/blog/cwtch-stable-roadmap-update-june). For an overview of how Cwtch works, watch the video above. The [Cwtch Handbook](https://docs.cwtch.im/) will tell you everything you need to know to use it. Cwtch is designed with metadata protection in mind; it is peer-to-peer, uses the Tor network as a shield, and stores everything locally on the device, encrypted.
+
+
+
+
+
How Cwtch works
+
+
+
Like all peer-to-peer communication, Cwtch requires *[synchronous](/glossary/#synchronous-communication)* communication, meaning that both peers must be online at the same time. However, its server feature also allows *[asynchronous](/glossary/#asynchronous-communication)* communication by providing offline delivery:
>"Cwtch contact to contact chat is fully peer to peer, which means if one peer is offline, you cannot chat, and there is no mechanism for multiple people to chat. To support group chat (and offline delivery) we have created untrusted Cwtch [servers](https://docs.cwtch.im/security/components/cwtch/server) which can host messages for a group. [...] the server has no way to know what messages for what groups it might be holding, or who is accessing it."