diff --git a/xep-0205.xml b/xep-0205.xml
index 1d9755d3..85416e96 100644
--- a/xep-0205.xml
+++ b/xep-0205.xml
@@ -130,7 +130,7 @@
   </section2>
   <section2 topic='Multiple Recipients' anchor='rec-recipients'>
     <p>A server implementation SHOULD enable a server administrator to limit the number of XML stanzas that a connected client may send to distinct recipients within a given time period.</p>
-    <p>If a connected client sends too many stanzas to distinct recipients in a given time period, the receiving server SHOULD NOT process the stanza and instead SHOULD return a &unexpected; stanza error, which in turn SHOULD include an application-specific error condition of &lt;too-many-stanzas/&gt;, as shown in the following example:</p>
+    <p>If a connected client sends too many stanzas to distinct recipients in a given time period, the receiving server SHOULD NOT process the stanza and instead SHOULD return an &unexpected; stanza error, which in turn SHOULD include an application-specific error condition of &lt;too-many-stanzas/&gt;, as shown in the following example:</p>
     <example caption='Stanza recipients violation: stanza error'><![CDATA[
 <message from='iago@shakespeare.lit/evilos' to='juliet@capulet.lit'>
   <error type='wait'>
@@ -197,6 +197,6 @@
   ]]></code>
 </section1>
 <section1 topic='Acknowledgements' anchor='ack'>
-  <p>Special thanks to Chris Mullins for calling attention to the need for a specification detailing best practices such as those recommended herein. Thanks also to Thiago Camargo, Bruce Campbell, Gustavo Felisberto, Justin Karneges, Pedro Melo, Kevin Smith, and Michael Vorner for their suggestions.</p>
+  <p>Special thanks to Chris Mullins for calling attention to the need for a specification detailing best practices such as those recommended herein. Thanks also to Thiago Camargo, Bruce Campbell, Gustavo Felisberto, Justin Karneges, Pedro Melo, Kevin Smith, and Michal Vaner for their suggestions.</p>
 </section1>
 </xep>