diff --git a/xep-0045.xml b/xep-0045.xml
index 3c2ca400..50db66d6 100644
--- a/xep-0045.xml
+++ b/xep-0045.xml
@@ -1905,7 +1905,7 @@
     id='ng91xs69'
     to='coven@chat.shakespeare.lit/thirdwitch'/>
 ]]></example>
-      <p>This behavior can not be distinguished from a presence update from a MUC-supporting client that was desynchronized from the room. Treating this as a groupchat 1.0 join will mask the error and leave the client in a partially-synchronized state. Therefore, starting with version 1.32 of this specification, it is RECOMMENDED that a service receiving a &lt;presence&gt; without an &lt;x&gt; element from a non-occupant full-JID responds with an explicit kick to that client.</p>
+      <p>This behavior can not be distinguished from a presence update from a MUC-supporting client that was desynchronized from the room. Treating this as a groupchat 1.0 join will mask the error and leave the client in a partially-synchronized state. Therefore, starting with version 1.32 of this specification, it is RECOMMENDED that a service receiving a &lt;presence&gt; without an &lt;x&gt; element from a non-occupant full-JID responds with an explicit kick to that client. The kick MUST contain the status codes 110 (occupant's presence), 307 (kick), and 333 (kick due to technical problems).</p>
       <example caption='Service Response to groupchat 1.0 join / non-occupant presence update'><![CDATA[
 <presence
     from='coven@chat.shakespeare.lit/thirdwitch'
@@ -1917,6 +1917,7 @@
     </item>
     <status code='110'/>
     <status code='307'/>
+    <status code='333'/>
   </x>
 </presence>
 ]]></example>