diff --git a/changelogs/client_server/newsfragments/2381.clarification b/changelogs/client_server/newsfragments/2381.clarification
new file mode 100644
index 00000000..e5215362
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2381.clarification
@@ -0,0 +1 @@
+Add links from the Client-Server spec to the Olm message definitions.
\ No newline at end of file
diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md
index 67313bbf..ec86203d 100644
--- a/content/client-server-api/modules/end_to_end_encryption.md
+++ b/content/client-server-api/modules/end_to_end_encryption.md
@@ -1623,9 +1623,9 @@ An event encrypted using Olm has the following format:
 ```
 
 `ciphertext` is a mapping from device Curve25519 key to an encrypted
-payload for that device. `body` is a Base64-encoded Olm message body.
+payload for that device. `body` is a Base64-encoded [Olm message body](/olm-megolm/olm/#the-olm-message-format).
 `type` is an integer indicating the type of the message body: 0 for the
-initial pre-key message, 1 for ordinary messages.
+initial [pre-key message](/olm-megolm/olm/#pre-key-messages), 1 for [normal messages](/olm-megolm/olm/#normal-messages).
 
 Olm sessions will generate messages with a type of 0 until they receive
 a message. Once a session has decrypted a message it will produce