From 97454eb280845f9e4fa5ae55b12de43b14ce8669 Mon Sep 17 00:00:00 2001
From: Florian Schmaus <flo@geekplace.eu>
Date: Wed, 14 Feb 2018 22:48:36 +0100
Subject: [PATCH] XEP-0300: Address feedback from PSA

---
 xep-0300.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xep-0300.xml b/xep-0300.xml
index 86d4f227..87e48e5a 100644
--- a/xep-0300.xml
+++ b/xep-0300.xml
@@ -26,7 +26,7 @@
   &tobias;
   <revision>
     <version>0.5.3</version>
-    <date>2017-10-04</date>
+    <date>2018-02-14</date>
     <initials>fs</initials>
     <remark><p>Clarify textual content of the &lt;hash/&gt; element.</p></remark>
   </revision>
@@ -131,7 +131,7 @@
       <td>&rfc7693;</td>
     </tr>
   </table>
-  <p>The digest produced by the used hash algorithm is included as the XML character data of the &lt;hash/&gt; after being encoded as Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype <note>See &lt;<link url='http://www.w3.org/TR/xmlschema-2/#base64Binary'>http://www.w3.org/TR/xmlschema-2/#base64Binary</link>&gt;.</note> as defined in &w3xmlschema2;.</p>
+  <p>The digest produced by the used hash algorithm is included as the XML character data of the &lt;hash/&gt; element after being encoded using Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype <note>See &lt;<link url='http://www.w3.org/TR/xmlschema-2/#base64Binary'>http://www.w3.org/TR/xmlschema-2/#base64Binary</link>&gt;.</note> as defined in &w3xmlschema2;. The Base64 output MUST NOT include whitespace and MUST set padding bits to zero.</p>
 </section1>
 
 <section1 topic='Hash Functions' anchor='hashes'>