From 90fff6b71fe57cabdf7f2beb58a2c74361be8d1f Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Fri, 6 Jan 2012 10:59:04 -0700
Subject: [PATCH] 0.0.1

---
 inbox/psa.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/inbox/psa.xml b/inbox/psa.xml
index 3fc636a6..4c249d97 100644
--- a/inbox/psa.xml
+++ b/inbox/psa.xml
@@ -29,7 +29,7 @@
   </revision>
 </header>
 <section1 topic='Introduction' anchor='intro'>
-  <p>Presence data received by a client are typically cached and displayed until they are replaced by an update (whereupon the new data will be cached and displayed...), for example graphically annotating availability of contacts in a roster. Where the entity from which the client has received the presence data is remote (residing upon a different server), unavailability of the server to server link will render the client unable to receive further presence updates from the entity but unaware that this is the case. Where the remote entity is a contact, it may cause the contact appear to be online (or offline, or away etc.) to the user of the client when they are not. Where the remote entity is a MUC room the case is more severe, as the MUC room may have ejected the client due to the S2S link being unavailable to send stanzas but the client may still consider itself present in the room.</p>
+  <p>Presence data received by a client &xmppim; are typically cached and displayed until they are replaced by an update (whereupon the new data will be cached and displayed...), for example graphically annotating availability of contacts in a roster. Where the entity from which the client has received the presence data is remote (residing upon a different server), unavailability of the server to server link will render the client unable to receive further presence updates from the entity but unaware that this is the case. Where the remote entity is a contact, it may cause the contact appear to be online (or offline, or away etc.) to the user of the client when they are not. Where the remote entity is a &xep0045; room the case is more severe, as the MUC room may have ejected the client due to the server-to-server (S2S) link being unavailable to send stanzas but the client may still consider itself present in the room.</p>
   <p>This extension provides a simple mechanism by which the local server can resend previous presence data to the client, annotated such that the client knows it would be unable to receive future updates.</p>
 </section1>
 Appropriate action - alert user, attempt to rejoin MUC, whatever.