From 158106279f15255750c1488a2dedb36cc900fd62 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 6 Aug 2025 15:44:50 +0100 Subject: [PATCH] Ensure it is clear that themost recent **valid** replacement should be used Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- content/client-server-api/modules/event_replacements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md index bce7e9fc..2e36e40e 100644 --- a/content/client-server-api/modules/event_replacements.md +++ b/content/client-server-api/modules/event_replacements.md @@ -268,7 +268,7 @@ Client authors are reminded to take note of the requirements for [Validity of replacement events](#validity-of-replacement-events), and to ignore any invalid replacement events that are received. -Clients should render the content of the **most recent** replacement event. The +Clients should render the content of the **most recent** valid replacement event. The most recent event is determined by comparing `origin_server_ts`; if two or more replacement events have identical `origin_server_ts`, the event with the lexicographically largest `event_id` is treated as more recent.