diff --git a/proposals/XXXX-disabled-presence-state.md b/proposals/4042-disabled-presence-state.md
similarity index 73%
rename from proposals/XXXX-disabled-presence-state.md
rename to proposals/4042-disabled-presence-state.md
index 8bb5ddd5..32b87f5d 100644
--- a/proposals/XXXX-disabled-presence-state.md
+++ b/proposals/4042-disabled-presence-state.md
@@ -1,14 +1,14 @@
-# MSC0000: Disabled Presence State
+# MSC4042: Disabled Presence State
 
 In current matrix we have no way to tell clients that we simply do not have presence data at all
 for a given homeserver or user. This proposal addresses this fact by adding a `disabled` state.
 
 By adding a `disabled` state to presence it allows us to kill two birds with one stone. Its used for
-MSC_PRESENCE_OVERRIDE_PLACEHOLDER and for this proposal. In this proposal its simply used to indicate
-a lack of information about a given user. This is going to 9 times out of 10 be because of that presence
-is disabled somewhere in the chain and therefore you cant get data. Be that disabled by the other user
-or their server or your server. If you are on matrix.org for example all presence will return this value
-if this proposal is adopted until they reenable presence. Since they have presence disabled.
+MSC4043 and for this proposal. In this proposal its simply used to indicatea lack of information about 
+a given user. This is going to 9 times out of 10 be because of that presence is disabled somewhere in the 
+chain and therefore you cant get data. Be that disabled by the other user or their server or your server.
+If you are on matrix.org for example all presence will return this value if this proposal is adopted until 
+they reenable presence. Since they have presence disabled.
 
 
 ## Proposal
@@ -20,7 +20,7 @@ Due to `unavailable` being taken for another use `disabled` became the best cand
 
 `disabled` presence should be used if data is missing. Be that due to presence being disabled or because of other
 mechanisms this state was selected. For example due to the user choosing to put this as their state via
-MSC_PRESENCE_OVERRIDE_PLACEHOLDER or other mechanism like this. 
+MSC4043 or other mechanism like this. 
 
 
 ## Potential issues
@@ -44,9 +44,9 @@ does not it self change anything in practice. Presence being disabled is not a s
 
 ## Unstable prefix
 
-Unstable implementations will use the state of `support.feline.mscXXXX.v1.disabled` in place of `disabled`.
+Unstable implementations will use the state of `support.feline.msc4042.v1.disabled` in place of `disabled`.
 
 ## Dependencies
 
-This MSC does not have any direct dependencies but is paired with MSC_PRESENCE_OVERRIDE_PLACEHOLDER due to
+This MSC does not have any direct dependencies but is paired with MSC4043 due to
 this MSC being a semi dependency for it. These proposals can be adopted independently.