From ac15b0e107fd381d0ffaab1f73863ea9751bb54e Mon Sep 17 00:00:00 2001
From: M66B <M66B@users.noreply.github.com>
Date: Tue, 2 Mar 2021 16:33:35 +0100
Subject: [PATCH] Updated FAQ

---
 FAQ.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/FAQ.md b/FAQ.md
index 1d59950fda..abb1304469 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -819,8 +819,11 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
 
 *pretty Easy privacy*
 
-There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this.
-Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
+There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people use it.
+
+However, FairEmail can send and receive PGP encrypted messages, which is compatible with p≡p.
+Also, FairEmail understands incoming p≡p messages since version 1.1519,
+so the encrypted subject will be shown and the embedded message text will be shown more nicely.
 
 <br />