From 0ab49d3b52bd846dfee360f888b6e224cd8e68a8 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Fri, 11 Jan 2008 16:29:56 +0000
Subject: [PATCH] typo

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

diff --git a/xep-0223.xml b/xep-0223.xml
index 2ca7fcfb..93598a4b 100644
--- a/xep-0223.xml
+++ b/xep-0223.xml
@@ -44,7 +44,7 @@
     <p>&xep0163; introduced the idea of a virtual &xep0060; service associated with an IM user's bare JID (&BAREJID;). However, personal eventing (PEP) is not optimized for the persistent storage of data objects that are meant to be accessed only by the account owner, &#224; la &xep0049;. Therefore this document defines a set of best practices that enable a user to persistently store private information at their virtual pubsub service; in effect, we "sub-class" PEP by showing how a particular pubsub node can be configured for storing private information (we call such a node a "PIP node").</p>
   </section2>
   <section2 topic='How It Works' anchor='howitworks'>
-    <p>This section provides a friendly introduction to privata information via pubsub (a.k.a. PIP).</p>
+    <p>This section provides a friendly introduction to private information via pubsub (a.k.a. PIP).</p>
     <p>Imagine that you are a Shakespearean character named Juliet and that you want to persistently store some private information such as bookmarks (&xep0048;).</p>
     <p>We assume that your server (capulet.lit) supports PEP along with the "publish-options" feature, and that your client discovered that support when you logged in.</p>
     <p>You want to start bookmarking &xep0045; rooms so your client stores that data privately:</p>