clarify that replacement event is Megolm message plaintext

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
link to m.room.encrypted for Olm and Megolm content
2026-08-04 15:07:47 +02:00 · 2026-07-20 11:10:38 +02:00 · 2026-07-20 10:51:07 +02:00
2 changed files with 3 additions and 3 deletions
--- a/content/client-server-api/modules/end_to_end_encryption.md
+++ b/content/client-server-api/modules/end_to_end_encryption.md
@ -1723,7 +1723,7 @@ Devices that support Olm must include "m.olm.v1.curve25519-aes-sha2" in
 their list of supported messaging algorithms, must list a Curve25519
 device key, and must publish Curve25519 one-time keys.

-The content of an event encrypted using Olm has the following format:
+The content of an [`m.room.encrypted`](#mroomencrypted) event using Olm has the following format:

 ```json
 {
@ -1896,7 +1896,7 @@ This uses:
 Devices that support Megolm must support Olm, and include
 "m.megolm.v1.aes-sha2" in their list of supported messaging algorithms.

-The content of an event encrypted using Megolm has the following format:
+The content of an [`m.room.encrypted`](#mroomencrypted) event using Megolm has the following format:

 ```json
 {
--- a/content/client-server-api/modules/event_replacements.md
+++ b/content/client-server-api/modules/event_replacements.md
@ -97,7 +97,7 @@ For example, a replacement for an encrypted event might look like this:
 }
 ```

-... and, once decrypted, the event might look like this:
+... and the plaintext body of the Megolm message might look like this:

 ```json
 {
Author	SHA1	Message	Date
gewitternacht	02ce04f083	clarify that replacement event is Megolm message plaintext Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>	2026-07-20 11:10:38 +02:00
Johanna Stuber	a692b7be83	link to m.room.encrypted for Olm and Megolm content Signed-off-by: Johanna Stuber <johannas@element.io>	2026-07-20 10:51:07 +02:00