From 6453ca95f0e4c886eb75161a49e1040cd9472c82 Mon Sep 17 00:00:00 2001
From: He4eT <He4eT@oddsquat.org>
Date: Thu, 23 Apr 2026 18:03:15 +0200
Subject: [PATCH] posts: encrypted_XMPP: review fixes

---
 src/pages/posts/2026/encrypted_XMPP.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/pages/posts/2026/encrypted_XMPP.md b/src/pages/posts/2026/encrypted_XMPP.md
index 74a34bf..12260d7 100644
--- a/src/pages/posts/2026/encrypted_XMPP.md
+++ b/src/pages/posts/2026/encrypted_XMPP.md
@@ -129,7 +129,8 @@ OMEMO is&nbsp;based on&nbsp;the <a
 While the internal details are quite interesting,
 for practical purposes it’s enough to&nbsp;know that
 each client stores some cryptographic keys
-and can derive a&nbsp;hash from them, commonly called a&nbsp;fingerprint.
+and can derive a&nbsp;human-readable hash from them,
+commonly called a&nbsp;fingerprint.
 
 Keys are usually managed automatically by&nbsp;the XMPP client,
 and in&nbsp;normal use you should never need to&nbsp;handle them manually.