From 73a62049e0b7a241ba876573b92f071f7065e641 Mon Sep 17 00:00:00 2001
From: "Matthew A. Miller" <linuxwolf@outer-planes.net>
Date: Thu, 13 Aug 2015 14:57:13 -0600
Subject: [PATCH] fix missing entity reference

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

diff --git a/xep-0247.xml b/xep-0247.xml
index 8f84a70d..f72bc9cc 100644
--- a/xep-0247.xml
+++ b/xep-0247.xml
@@ -53,7 +53,7 @@
     <li>Two endpoints want to enforce end-to-end encryption</li>
     <li>Two endpoints want to send a high volume of XMPP traffic but the intermediate servers enforce rate limits</li>
   </ul>
-  <p>The first situation is addressed by &xep0174;. However, if the endpoints already have client-to-server connections but wish to bypass those connections or leverage those streams for a higher-level application such as end-to-end encryption, it is desirable for the two endpoints to negotiate an end-to-end XML stream. This specification defines methods for doing so, where the application format is an XML stream and the transport method is any direct or mediated streaming transport, such as &xep0261; (mediated), &xep0260; (direct or mediated), or a future ice-tcp Jingle transport (direct or mediated) based on &ice-tcp;.</p>
+  <p>The first situation is addressed by &xep0174;. However, if the endpoints already have client-to-server connections but wish to bypass those connections or leverage those streams for a higher-level application such as end-to-end encryption, it is desirable for the two endpoints to negotiate an end-to-end XML stream. This specification defines methods for doing so, where the application format is an XML stream and the transport method is any direct or mediated streaming transport, such as &xep0261; (mediated), &xep0260; (direct or mediated), or a future ice-tcp Jingle transport (direct or mediated) based on &rfc6544;.</p>
 </section1>
 
 <section1 topic='Protocol' anchor='protocol'>