diff --git a/inbox/muc-selfping.xml b/inbox/muc-selfping.xml
index 16cd2284..c5f0d474 100644
--- a/inbox/muc-selfping.xml
+++ b/inbox/muc-selfping.xml
@@ -6,7 +6,7 @@
 <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
 <xep>
 <header>
-  <title>Schrödinger's Chat</title>
+  <title>MUC Self-Ping (Schrödinger's Chat)</title>
   <abstract>This protocol extension for XEP-0045 Multi User Chat allows clients to check whether they are still joined to a chatroom.</abstract>
   &LEGALNOTICE;
   <number>xxxx</number>
@@ -28,6 +28,12 @@
     <email>georg@op-co.de</email>
     <jid>georg@yax.im</jid>
   </author>
+  <revision>
+    <version>0.0.2</version>
+    <date>2018-08-06</date>
+    <initials>gl</initials>
+    <remark><p>Add handling for another corner case, change title to Council’s liking</p></remark>
+  </revision>
   <revision>
     <version>0.0.1</version>
     <date>2018-07-31</date>
@@ -141,6 +147,9 @@
       <li><strong>Error (&lt;service-unavailable&gt; or
 	  &lt;feature-not-implemented&gt;)</strong>: the client is joined, but
 	the pinged client does not implement &xep0199;.</li>
+      <li><strong>Error (&lt;item-not-found&gt;)</strong>: the client is
+	joined, but the participant just changed their name (e.g. initiated by
+	a different client).</li>
       <li><strong>Any other error</strong>: the client is probably not
 	joined.</li>
       <li><strong>Timeout (no response)</strong>: the MUC service (or another
@@ -161,6 +170,16 @@
       opposed to routing it to any of the participant's clients.</p>
   </section2>
 </section1>
+<section1 topic='Implementation Notes' anchor='impl'>
+  <p>In Multi-Session-Nick scenarios, where multiple clients of the same user
+    are joined as the same participant, it is possible that another client
+    initiates a nickname change while a ping request is pending. In that case,
+    the ping might be responded to with &lt;item-not-found&gt;.</p>
+  <p>A client should not perform a self-ping after initiating a nickname
+    change, and before receiving the response to the nickname change from the
+    service, as it is not yet clear whether the new nickname will be accepted.
+  </p>
+</section1>
 <section1 topic='Security Considerations' anchor='security'>
   <p>A MUC service implementation should not allow a non-participant to obtain
     information about participants. This is however true irregardless of