From 8d101fd9589dc7548a4af933302b348044d1ce20 Mon Sep 17 00:00:00 2001
From: Kegan Dougal <7190048+kegsay@users.noreply.github.com>
Date: Fri, 19 Sep 2025 11:02:48 +0100
Subject: [PATCH] Update 4354-sticky-events.md

---
 proposals/4354-sticky-events.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/proposals/4354-sticky-events.md b/proposals/4354-sticky-events.md
index 5eff6f57e..d497ae765 100644
--- a/proposals/4354-sticky-events.md
+++ b/proposals/4354-sticky-events.md
@@ -38,7 +38,8 @@ Message events can be annotated with a new top-level `sticky` key[^toplevel], wh
 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
-event to make it happen.
+event to make it happen. The `sticky` key is not protected from redaction. A redacted sticky event is the same
+as a normal event.
 
 ```json
 {