From 8d99dcaa423e307ed7785fb1c9b624fb83854c12 Mon Sep 17 00:00:00 2001
From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com>
Date: Sun, 24 Jul 2022 22:46:03 +0200
Subject: [PATCH] Improve Post merge information

Added improved information about what to do after the MSC gets merged.
---
 .../3784-using-room-type-of-m.policy-for-policy-rooms.md    | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md
index 4640a08e..5c292e2d 100644
--- a/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md
+++ b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md
@@ -55,8 +55,10 @@ implications should be minimal.
 ## Unstable prefix
 
 If you want to implement this MSC before its merged your free to use the unstable type of 
-`support.feline.policy.lists.msc.v1` please note that stakeholders are under no obligation to support this
-unstable prefix after this MSC gets merged as of time of writing. 
+`support.feline.policy.lists.msc.v1`. 
+
+After this MSC gets merged if a stakeholder has elected to remove its support for the unstable prefix if any
+support existed or support never existed revert to Legacy room behavior for rooms that used the unstable prefix.
 
 ## Dependencies