From e4ebe6c2e6c48f2cc2540dafc8874ebae2db2373 Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Wed, 7 Mar 2012 18:46:29 -0700
Subject: [PATCH] corrected a typo

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

diff --git a/xep-0133.xml b/xep-0133.xml
index a75dda38..ee8e7080 100644
--- a/xep-0133.xml
+++ b/xep-0133.xml
@@ -1554,7 +1554,7 @@
     <p>The service MAY specify additional fields that restrict the scope of the user list (e.g., regular expression matching for Jabber IDs), and such fields MAY be registered in the future with the XMPP Registrar; however, such fields are not defined herein.</p>
   </section2>
   <section2 topic='Get List of Online Users' anchor='get-online-users-list'>
-    <p>It may be helpful to enable an administrator to retrieve a list of all online users. Because the number of online users may be quite large, the service may need to truncate the result-set, since it could be quite large (however, any ability to limit or page through the result-set is outside the scope of this document). The command node for this use case SHOULD be "http://jabber.org/protocol/admin#get-online-users".</p>
+    <p>It may be helpful to enable an administrator to retrieve a list of all online users. Because the number of online users may be quite large, the service may need to truncate the result-set, since it could be quite large (however, any ability to limit or page through the result-set is outside the scope of this document). The command node for this use case SHOULD be "http://jabber.org/protocol/admin#get-online-users-list".</p>
     <p>A sample protocol flow for this use case is shown below.</p>
     <example caption='Admin Requests List of Online Users'><![CDATA[
 <iq from='bard@shakespeare.lit/globe'