Small clarification

Author: Johennes

proposals/4075-rtc-notification-event.md

@@ -357,7 +357,7 @@ mitigate this by adapting their push rules, [ignoring] the sender or leaving the
 | Directing invites at specific users | ✅ via `invitee` on [`m.call.invite`] | ✅ via `m.mentions` on `m.rtc.invite` |
 | Expiring invites | ⚠️ via `lifetime` on [`m.call.invite`] evaluated against [`age`] which is known to be broken in various homeservers | ✅ via `lifetime` on `m.rtc.invite` evaluated against either `sender_ts` or `origin_server_ts` |
 | Inviting without starting a call | ❌ Not possible | ✅ Explicitly allowed if an open slot exists |
-| Withdrawing invites | ✅ via [`m.call.hangup`] events | ✅ via empty `m.rtc.invite` events |
+| Withdrawing invites | ✅ via [`m.call.hangup`] events | ✅ via empty or redacted `m.rtc.invite` events |
 | Declining invites | ✅ via [`m.call.hangup`] events | ✅ via `m.rtc.decline` events |
 | Notifications in default rooms | ✅ via `.m.rule.call` push rule | ✅ via `.m.rule.rtc.invite_for_me`, `.m.rule.rtc.invite_for_room` or `.m.rule.rtc.invite` push rules |
 | Notifications in mentions-only rooms | ❌ Not possible | ✅ via `.m.rule.rtc.invite_for_me` and `.m.rule.rtc.invite_for_room` push rules |