From 7a7a8e9b23b0dcbfdf1a08426c8b96d96396363c Mon Sep 17 00:00:00 2001
From: Melvin Keskin <melvo@olomono.de>
Date: Fri, 22 Mar 2019 19:45:16 +0100
Subject: [PATCH] improve glossary

---
 inbox/automatic-trust-transfer.xml | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/inbox/automatic-trust-transfer.xml b/inbox/automatic-trust-transfer.xml
index b0ce34f3..c715faa5 100644
--- a/inbox/automatic-trust-transfer.xml
+++ b/inbox/automatic-trust-transfer.xml
@@ -120,8 +120,20 @@
 			<dd>
 				OMEMO message which indicates that specific keys can be trusted (authentication) or no longer trusted (revocation).
 				A trust message for a device's key sent to another device is a trust message that contains the key identifer of the given key for authentication or revocation.
-				If a trust message only contains key identifiers for authentication, it is called <cite>authentication message</cite>.
-				If it only contains key identifiers for revocation, it is called <cite>revocation message</cite>.
+			</dd>
+		</di>
+		<di>
+			<dt>Authentication message</dt>
+			<dd>
+				Trust message which only contains key identifiers for authentication.
+				If a trust message contains authentication and revocation parts, the term authentication message is used for referring to the trust message without revocation parts.
+			</dd>
+		</di>
+		<di>
+			<dt>Revocation message</dt>
+			<dd>
+				Trust message which only contains key identifiers for revocation.
+				If a trust message contains authentication and revocation parts, the term revocation message is used for referring to the trust message without authentication parts.
 			</dd>
 		</di>
 	</dl>