From 244d35914a75271467047c3a7e5ff98174c92998 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Mon, 24 Sep 2007 21:35:15 +0000
Subject: [PATCH] 1.10pre10

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

diff --git a/xep-0060.xml b/xep-0060.xml
index e37477f8..e048905d 100644
--- a/xep-0060.xml
+++ b/xep-0060.xml
@@ -49,8 +49,8 @@
   &ralphm;
 
   <revision>
-    <version>1.10pre9</version>
-    <date>in progress, last updated 2007-09-12</date>
+    <version>1.10pre10</version>
+    <date>in progress, last updated 2007-09-24</date>
     <initials>psa</initials>
     <remark>
       <ul>
@@ -5792,7 +5792,7 @@ O, what a rogue and peasant slave am I!
     ]]></example>
   </section2>
   <section2 topic='Singleton Nodes' anchor='impl-singleton'>
-    <p>For some nodes where the NodeID is an XML namespace (e.g., as used in <cite>XEP-0163</cite>), it is desirable to have at most one item associated with the node at any one time (for example, a client may want to store its preferences using a node name that is a namespace controlled by that client). When this pattern is desired, it is RECOMMENDE for the publisher to specify an ItemID of "SINGLETON" to ensure that the publication of a new item will overwrite the existing item.</p>
+    <p>For some nodes, it is desirable to have at most one item associated with the node at any one time (for example, a client may want to store its preferences using a node name that is a namespace controlled by that client). When this pattern is desired, it is RECOMMENDED for the publisher to specify an ItemID of "current" to ensure that the publication of a new item will overwrite the existing item.</p>
   </section2>
 </section1>