From 42ecaa698441803f089ce64ff030bddb5ecf7ed9 Mon Sep 17 00:00:00 2001
From: Sergey Ilinykh <rion4ik@gmail.com>
Date: Mon, 21 Jan 2019 23:55:18 +0300
Subject: [PATCH] Update description for example with hash-used

---
 xep-0234.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0234.xml b/xep-0234.xml
index 46d6c389..819a61c9 100644
--- a/xep-0234.xml
+++ b/xep-0234.xml
@@ -854,7 +854,7 @@ a=file-range:1024-*]]></code>
     </checksum>
   </jingle>
 </iq>]]></example>
-    <p>If the initiator wishes to communicate only the hashing algorithm at the beginning of the session (e.g., because it has not yet calculated the checksum), it can send an empty &lt;hash/&gt; element (without a checksum in the XML character data as shown in the previous examples) in the session-initiate message; this enables the recipient to check the file during the transfer session (which can be helpful in the case of transfers that are truncated or fail mid-stream).</p>
+    <p>If the initiator wishes to communicate only the hashing algorithm at the beginning of the session (e.g., because it has not yet calculated the checksum), it can send &lt;hash-used/&gt; element in the session-initiate message; this enables the recipient to check the file during the transfer session (which can be helpful in the case of transfers that are truncated or fail mid-stream).</p>
     <example caption="Initiator communicates hashing algorithm in session-initiate"><![CDATA[
 <iq from='romeo@montague.example/dr4hcr0st3lup4c'
     id='nzu25s8'