From 339bfca857b561a1dfa94594f0334dd72f2d4777 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Thu, 27 Sep 2007 19:50:48 +0000
Subject: [PATCH] removed NSNOTE

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1253 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0184.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/xep-0184.xml b/xep-0184.xml
index 4f949a3c1..b145904e7 100644
--- a/xep-0184.xml
+++ b/xep-0184.xml
@@ -83,7 +83,7 @@
   <p>Note: This document explicitly does not define a protocol for "guaranteed delivery", since that term (like "security") means different things to different people. Instead, we define a more focused protocol that addresses the need for message receipts, thus solving one problem that falls under the heading of "guaranteed delivery".</p>
 </section1>
 <section1 topic='Protocol Format' anchor='format'>
-  <p>In order to make it possible for senders to request and for recipients to generate message receipts, we define a dedicated protocol extension qualified by the 'urn:xmpp:receipts' namespace &NSNOTE;.</p>
+  <p>In order to make it possible for senders to request and for recipients to generate message receipts, we define a dedicated protocol extension qualified by the 'urn:xmpp:receipts' namespace.</p>
   <p>There are two allowable elements in this namespace:</p>
   <ul>
     <li>&lt;request/&gt; -- included by a sending entity that wishes to know if the message has been received.</li>
@@ -122,7 +122,7 @@
 </section1>
 <section1 topic='Determining Support' anchor='disco'>
   <p>If a sender wishes to request message receipts, it SHOULD first determine whether the intended recipient supports message receipts. This can be done directly via <cite>Service Discovery</cite> or indirectly via <cite>Entity Capabilities</cite>.</p>
-  <p>If an entity supports message receipts, it MUST report that by including a service discovery feature of "urn:xmpp:receipts" in response to disco#info requests &NSNOTE;:</p>
+  <p>If an entity supports message receipts, it MUST report that by including a service discovery feature of "urn:xmpp:receipts" in response to disco#info requests:</p>
   <example caption="Initial Service Discovery information request"><![CDATA[
 <iq from='northumberland@shakespeare.lit/westminster'
     to='kingrichard@royalty.england.lit/throne'
@@ -143,7 +143,7 @@
   ]]></example>
 </section1>
 <section1 topic='Negotiation' anchor='neg'>
-  <p>Two entities MAY negotiate the use of message receipts for a given session using <cite>Stanza Session Negotiation</cite>. The parameter to be negotiated is named "urn:xmpp:receipts" &NSNOTE;. Its use is illustrated in the following examples.</p>
+  <p>Two entities MAY negotiate the use of message receipts for a given session using <cite>Stanza Session Negotiation</cite>. The parameter to be negotiated is named "urn:xmpp:receipts". Its use is illustrated in the following examples.</p>
   <example caption="User requests chat session"><![CDATA[
 <message type='normal'
          from='northumberland@shakespeare.lit/westminster'