diff --git a/xep-0369.xml b/xep-0369.xml
index 04876db3..86dc9ba8 100644
--- a/xep-0369.xml
+++ b/xep-0369.xml
@@ -36,6 +36,14 @@
&ksmithisode;
&skille;
&stpeter;
+
+ Fix typo errors with single quotes (marj). Editorial fixes (ralph)
+
A user setting status is now used as an example. Unlike in &xep0045; where coming online is a special action, coming online in MIX is implicit when presence status is set. Going offline is a achieved by setting presence status to unavailable, which removes the client full JID entry from the presence node. When a user sets a presence status, the user's server sends updated presence to the MIX channel, and the MIX service then publishes the user's availability to the "urn:xmpp:mix:nodes:presence" node. If there is not an item named by the full JID of the client with updated presence status, this item is created. The sequence is shown in the following examples, starting with a client setting presences status on the connected server.
Owners and Administrators are allowed to control which users can participate in a channel by use of Allowed and Banned lists using PubSub. These operations follow &xep0060; which sets out detailed protocol use and error handling.
Allowed and Banned lists MAY be read by PubSub get of the Banned and Allowed Nodes. This operation MAY be used by users as controlled by 'Allowed Node Subscription' and 'Banned Node Subscription' configuration node options (default Administrators).
@@ -2411,7 +2419,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
JIDs can be removed from the Allowed and Banned nodes by pubsub retract command.
-