typo

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1109 4b5297f7-1745-476d-ba37-a9c6900126ab

xep-0163.xml

@@ -149,8 +149,7 @@
     <p class='em'>Note: Any use cases not described herein are described in <cite>XEP-0060</cite>. Also, this document does not show error flows related to the generic publish-subscribe use cases referenced herein, since they are exhaustively defined in <cite>XEP-0060</cite>. The reader is referred to <cite>XEP-0060</cite> for all relevant protocol details related to the XMPP publish-subscribe extension. This document merely defines a "subset" or "profile" of XMPP publish-subscribe.</p>
   </section2>
   <section2 topic='How It Works' anchor='howitworks'>
-    <p>This section provides a friendly, non-normative introduction to the workings of personal eventing via pubsub (PEP).</p>
-    <p>There are two sides to personal eventing: what the user does to generate events and what the contact does to receive events. As shown in the following examples, both are simplified in PEP as compared to generic pubsub.</p>
+    <p>This section provides a friendly introduction to personal eventing via pubsub (PEP).</p>
     <p>Imagine that you are a Shakespearean character named Juliet and that you want to generate events about what music you're listening to, which anyone may see as long as they are authorized to see your online/offline presence (i.e., a pubsub access model of "presence").</p>
     <p>We assume that you have three contacts with the following relationship to you:</p>
     <ol start='1'>
@@ -430,7 +429,7 @@
       </item>
     </items>
   </event>
-  <x xmlns='jabber:x:delay' stamp='20031213T23:58:37'/>
+  <delay xmlns='urn:xmpp:delay' stamp='2003-12-13T23:58:37Z'/>
 </message>
       ]]></example>
     </section3>