From e92eed9e148303d5a8b9b27d4a394e34b6cb648a Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Wed, 26 Sep 2007 20:23:11 +0000
Subject: [PATCH] typo

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1239 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0184.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0184.xml b/xep-0184.xml
index 4c4f4023..4f949a3c 100644
--- a/xep-0184.xml
+++ b/xep-0184.xml
@@ -72,7 +72,7 @@
 </header>
 <section1 topic='Introduction' anchor='intro'>
   <p>While &xep0079; provides message acknowledgements at the server level, it does not extend that model all the way to the client. However, sometimes client-level acknowledgements are needed, for example to provide "receipts". This document defines a mechanism for XMPP message receipts, which are functionally equivalent to the "delivered" or "displayed" event in &xep0022;, which this specification in part obsoletes. <note>This specification does not distinguish between delivery and presentation, as was done in the message events protocol, in part because no existing clients make the distinction.</note></p>
-  <p>Note: This extension is functionally equivalent to an <cite>Advanced Message Processing</cite> rule of "receipt" but uses a dedicated namespace to simplify processing by end clients and intermediate routers.</p>
+  <p>Note: This extension is functionally equivalent to an <cite>Advanced Message Processing</cite> rule of "receipt" but uses a dedicated namespace to simplify processing by end user clients and intermediate routers.</p>
 </section1>
 <section1 topic='Requirements' anchor='reqs'>
   <p>This document addresses the following requirements:</p>