From 8f0e3ceb785786d71c568d70c59c8d7f3fdd27f7 Mon Sep 17 00:00:00 2001
From: Kegan Dougal <7190048+kegsay@users.noreply.github.com>
Date: Sat, 27 Sep 2025 08:51:25 +0100
Subject: [PATCH] Update proposals/4354-sticky-events.md

Co-authored-by: Timo <16718859+toger5@users.noreply.github.com>
---
 proposals/4354-sticky-events.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proposals/4354-sticky-events.md b/proposals/4354-sticky-events.md
index 920b8d622..e3cc49592 100644
--- a/proposals/4354-sticky-events.md
+++ b/proposals/4354-sticky-events.md
@@ -34,7 +34,7 @@ This new primitive can be used to implement MatrixRTC participation, live locati
 
 ## Proposal
 
-Message events can be annotated with a new top-level `sticky` key[^toplevel], which MUST have a `duration_ms`,
+Message events can be annotated with a new top-level `sticky` object[^toplevel], which MUST have a `duration_ms`,
 which is the number of milliseconds for the event to be sticky. The presence of `sticky.duration_ms`
 with a valid value makes the event “sticky”[^stickyobj]. Valid values are the integer range 0-3600000 (1 hour).
 For use cases that require stickiness beyond this limit, the application is responsible for sending another