From c7ca7ae079442d78ac3e37e0309b3123a48c69ab Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Date: Wed, 24 Jun 2026 10:53:24 +0100
Subject: [PATCH] Apply suggestion from @richvdh

---
 .../client-server-api/modules/end_to_end_encryption.md    | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

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 1ea8e33d..e1780ddd 100644
--- a/content/client-server-api/modules/end_to_end_encryption.md
+++ b/content/client-server-api/modules/end_to_end_encryption.md
@@ -1564,11 +1564,11 @@ before inviting him.
 Only room keys which were marked as "shareable" by the creator of the
 encryption session should be shared with new users.
 
-When Alice wants to send a message in the room she shares with Bob, she first
+When a user wants to send a message in an encrypted room, their client first
 checks the [history visibility](#room-history-visibility) state of the
-room. If it is `shared` or `world_readable`, then when she sends the Megolm
-keys to Bob via an [`m.room_key`](#mroom_key) message, she sets
-`shared_history` to `true`.
+room. If it is `shared` or `world_readable`, then when the client sends the Megolm
+keys to room members via [`m.room_key`](#mroom_key) messages, it SHOULD set
+`shared_history` to `true`. Otherwise, it SHOULD set `shared_history` to `false`.
 
 If the history visibility changes in a way that would affect the
 `shared_history` flag (i.e., it changes from `joined` or `invited` to `shared`