XEP-0300: Remove extra characters in example.

xep-0300.xml

@@ -83,7 +83,7 @@
 
 <section1 topic='XML Format' anchor='format'>
   <p>This document defines a new XML element that can be used in any XMPP protocol extension. An example follows.</p>
-  <code><![CDATA[<hash xmlns='urn:xmpp:hashes:2' algo='sha-256'>2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=</hash>åå]]></code>
+  <code><![CDATA[<hash xmlns='urn:xmpp:hashes:2' algo='sha-256'>2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=</hash>]]></code>
   <p>An XMPP protocol can include more than one instance of the &lt;hash/&gt; element, as long as each one has a different value for the 'algo' attribute:</p>
   <code><![CDATA[<hash xmlns='urn:xmpp:hashes:2' algo='sha-1'>2AfMGH8O7UNPTvUVAM9aK13mpCY=</hash>
 <hash xmlns='urn:xmpp:hashes:2' algo='sha-256'>2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=</hash>]]></code>
@@ -216,7 +216,7 @@
     type='get'>
   <query xmlns='http://jabber.org/protocol/disco#info'/>
 </iq>
-  ]]></example>
+]]></example>
   <example caption="Service discovery information response"><![CDATA[
 <iq from='juliet@capulet.lit/balcony'
     id='uw72g176'
@@ -228,7 +228,7 @@
     <feature var='urn:xmpp:hash-function-text-names:sha3-256'/>
   </query>
 </iq>
-  ]]></example>
+]]></example>
   <p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
 </section1>
 
@@ -363,7 +363,7 @@
   <desc>Support for the BLAKE2b-512 hashing algorithm</desc>
   <doc>XEP-0300</doc>
 </var>
-    ]]></code>
+]]></code>
   </section2>
 </section1>
 
@@ -388,7 +388,7 @@
   </xs:element>
 
 </xs:schema>
-  ]]></code>
+]]></code>
 </section1>
 
 <section1 topic='Acknowledgements' anchor='ack'>