From ce37b02f40b507c9b16f988f53e95963cc7558f7 Mon Sep 17 00:00:00 2001
From: Kegan Dougal <7190048+kegsay@users.noreply.github.com>
Date: Mon, 22 Sep 2025 14:46:55 +0100
Subject: [PATCH] Update 4354-sticky-events.md

---
 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 e1a34aa5b..14714e0cc 100644
--- a/proposals/4354-sticky-events.md
+++ b/proposals/4354-sticky-events.md
@@ -343,7 +343,7 @@ dropped updates for the latter scenario.
 - The `sticky` key in the PDU is `msc4354_sticky`.
 - The `/sync` response section is `msc4354_sticky_events`.
 - The sticky key in the `content` of the PDU is `msc4354_sticky_key`.
-- To enable this in SSS, the extension name is `org.matrix.msc4308.sticky_events`.
+- To enable this in SSS, the extension name is `org.matrix.msc4354.sticky_events`.
 
 [^toplevel]: This has to be at the top-level as we want to support _encrypted_ sticky events, and therefore metadata the server
 needs cannot be within `content`.