From b87c35353c9f4ae34342ea42eb1992c1aa15e88e Mon Sep 17 00:00:00 2001
From: Sam Whited <sam@samwhited.com>
Date: Mon, 11 Jul 2016 21:09:53 -0500
Subject: [PATCH] XEP-0366: Fix typos

Remove author info for Doug who no longer works at Atlassian.
Change author info for Sam to use the entity.
---
 xep-0366.xml | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/xep-0366.xml b/xep-0366.xml
index 0516d77b..c6e81dfd 100644
--- a/xep-0366.xml
+++ b/xep-0366.xml
@@ -25,17 +25,17 @@
   <supersedes />
   <supersededby />
   <shortname>EV</shortname>
-  <author>
-    <firstname>Sam</firstname>
-    <surname>Whited</surname>
-    <email>swhited@atlassian.com</email>
-    <jid>sam@samwhited.com</jid>
-  </author>
+  &sam;
   <author>
     <firstname>Doug</firstname>
     <surname>Keen</surname>
-    <email>dkeen@atlassian.com</email>
   </author>
+  <revision>
+    <version>0.1.1</version>
+    <date>2016-07-11</date>
+    <initials>ssw</initials>
+    <remark><p>Typo fixes.</p></remark>
+  </revision>
   <revision>
     <version>0.1</version>
     <date>2015-12-15</date>
@@ -87,7 +87,7 @@
       multiple versions of an entity list or maintain other redundant state.
     </li>
     <li>
-      Inconsistant state between servers in a cluster should not cause cache
+      Inconsistent state between servers in a cluster should not cause cache
       invalidation for the entire entity list.
     </li>
     <li>
@@ -101,10 +101,10 @@
     <dt>Aggregate Token</dt>
     <dd>
       A hash which represents the state of a list of entities, and changes if
-      any of those entities changes.
+      any of the entities change.
     </dd>
     <dt>Versioned Entity</dt>
-    <dd>Any abstract object which may be versioned (eg. rooms, users).</dd>
+    <dd>Any object which may be versioned (eg. rooms, users).</dd>
     <dt>Version Token</dt>
     <dd>
       A short, case sensitive string which represents an entity and changes if
@@ -244,7 +244,7 @@
       this document.  Similarly, clients MAY also add version nodes for each
       version token they possess to the request for a list (not specifying a
       version token will force the server to send information on that entity to
-      the client). If a server sends up a list of version tokens, the server
+      the client). If a client sends up a list of version tokens, the server
       MUST then check to see if those tokens correspond to any entity which it
       knows about, and not send down any entities with matching version tokens
       in the response.