From 6ff2428ca54e3800e3546a8901a379c7462e6978 Mon Sep 17 00:00:00 2001
From: Artem <189279532+jpcshka@users.noreply.github.com>
Date: Tue, 30 Jun 2026 13:12:12 +0300
Subject: [PATCH] Update data/event-schemas/schema/m.image_pack.rooms.yaml

Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
---
 data/event-schemas/schema/m.image_pack.rooms.yaml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/data/event-schemas/schema/m.image_pack.rooms.yaml b/data/event-schemas/schema/m.image_pack.rooms.yaml
index 4c23bbf3..b9f04fdd 100644
--- a/data/event-schemas/schema/m.image_pack.rooms.yaml
+++ b/data/event-schemas/schema/m.image_pack.rooms.yaml
@@ -20,8 +20,7 @@ properties:
           Each entry references a specific `m.room.image_pack` state event
           that the user has enabled globally.
 
-          The bottom-level object is reserved for future use by a subsequent
-          MSC. Clients MUST treat it as opaque and preserve any unrecognised
+          The bottom-level object is reserved for future use. Clients SHOULD treat it as opaque and preserve any unrecognised
           properties when modifying this event.
 
           A room ID present as a key but with no `state_key` entries (i.e. an