diff --git a/inbox/fastmuc.xml b/inbox/fastmuc.xml
index 94ea193f..edb99b5b 100644
--- a/inbox/fastmuc.xml
+++ b/inbox/fastmuc.xml
@@ -37,7 +37,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.
MUC Rooms supporting this should have a disco feature of "urn:xmpp:mfr" in caps. MUC Rooms supporting this should have a disco feature of "urn:xmpp:presence-session:0" in caps. To avoid extra roundtrips for discovery, clients may speculatively send elements when initially joining a MUC, and treat the absense of appropriate elements in the responses to indicate a lack of support.
If a client has indicated that it's using MUC Fast Reconnect on its session, the MUC service MUST annotate the presence stanzas it sends with elements containing a presence-session element with namespace "urn:xmpp:presence-session:0", a "session" attribute and an "id" attribute, described below.
@@ -60,7 +60,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.Attributes:
@@ -76,7 +76,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever. from='romeo@montague.lit/lane' to='orchard@chat.capulet.lit/Romeo'>When the MUC room receives a room fast rejoin request, it must either first send an 'unavailable' presence from the room's bare JID, followed by a normal full join, as above, or instead of sending the full presence list for all occupants, only send those stanzas needed to get from the state represented by the client-provided session and id to the current state. All the presence stanzas (apart from the unavailable one used to reset state before a clean join) MUST contain the presence-session element as described above.