Move into alphabetical order
Move into alphabetical order

--- a/docs/server-api.md
+++ b/docs/server-api.md
@@ -31,6 +31,50 @@
 -------------------
 
 
+### banUser
+
+Can only be called by the room admin, kicks a user out of the room, and does not allow them to return (unless re-invited)
+
+    {
+        "action":"banUser",
+        "payload": {    
+                    "roomName": "[name of room]",
+                    "user": user,
+                    "kick": [user to kick],
+                    "sesskey": sessionkey
+        }
+    }
+
+*Response*
+
+If successful, the value of `status` will be `ok` and the kicked user's session will be terminated and their user record removed. A message will be pushed to the room by `SYSTEM` to note that that user has been kicked and banned.
+
+If the requesting user lacks the privileges to kick a user, `SYSTEM` will push a message to warn that `user` tried to ban `tokick`.
+
+
+
+### closeRoom
+
+This can only be successfully called by the room's owner. `closeRoom` will close the current room, remove all associated messages, sessions and user accounts.
+
+
+    {
+        "action":"closeRoom",
+        "payload": {    
+                    "roomName": "[name of room]",
+                    "user": user,
+                    "sesskey": sessionkey
+        }
+    }
+
+*Response*
+
+If successful, the value of `status` will be `ok`.
+
+Rooms should always be closed when they are no longer required. The server will (by default) automatically close inactive rooms after a period, but this is intended as a safety net (in case the admin gets disconnected and cannot reconnect for some reason).
+
+
+
 ### createRoom
 
 This is used to create a room. Calls are currently unauthenticated because user accounts are tied to a room rather than existing in a global namespace (this is done to limit the risk of a list of possible users sitting on the server until they're likely to be needed).
@@ -52,6 +96,29 @@
 If the room is successfully created, the value of `status` will be `ok`. The roomname will also be confirmed back as the attribute `name`.
 
 The user will then need to call `joinRoom` in order to enter the room (the client could do this automatically, but the current client version does not).
+
+
+
+### inviteUser
+
+Used to invite a user into the current room. Can be called by admin's and users alike (`SYSTEM` will push a message into the room to notify others of the invite)
+
+    {
+        "action":"inviteUser",
+        "payload": {    
+                    "roomName": "[name of room]",
+                    "user": user,
+                    "invite": [user to invite],
+                    "pass": [new users pass]
+                    "sesskey": sessionkey
+        }
+    }
+
+When inviting a user, we need to specify their username as `invite` and their authentication password as `pass`
+
+*Response*
+
+If successful, the value of `status` will be `ok`. `SYSTEM` will also push a message into the room that `user` invited `invite`
 
 
 
@@ -89,57 +156,12 @@
 
 
 
-### closeRoom
-
-This can only be successfully called by the room's owner. `closeRoom` will close the current room, remove all associated messages, sessions and user accounts.
-
-
-    {
-        "action":"closeRoom",
-        "payload": {    
-                    "roomName": "[name of room]",
-                    "user": user,
-                    "sesskey": sessionkey
-        }
-    }
-
-*Response*
-
-If successful, the value of `status` will be `ok`.
-
-Rooms should always be closed when they are no longer required. The server will (by default) automatically close inactive rooms after a period, but this is intended as a safety net (in case the admin gets disconnected and cannot reconnect for some reason).
-
-
-
-### inviteUser
-
-Used to invite a user into the current room. Can be called by admin's and users alike (`SYSTEM` will push a message into the room to notify others of the invite)
-
-    {
-        "action":"inviteUser",
-        "payload": {    
-                    "roomName": "[name of room]",
-                    "user": user,
-                    "invite": [user to invite],
-                    "pass": [new users pass]
-                    "sesskey": sessionkey
-        }
-    }
-
-When inviting a user, we need to specify their username as `invite` and their authentication password as `pass`
-
-*Response*
-
-If successful, the value of `status` will be `ok`. `SYSTEM` will also push a message into the room that `user` invited `invite`
-
-
-
-### banUser
-
-Can only be called by the room admin, kicks a user out of the room, and does not allow them to return (unless re-invited)
-
-    {
-        "action":"banUser",
+### kickUser
+
+Can only be called by the room admin, kicks a user out of the room (but allows them to return). Useful where you think a user's session has hung (for example)
+
+    {
+        "action":"kickUser",
         "payload": {    
                     "roomName": "[name of room]",
                     "user": user,
@@ -150,38 +172,12 @@
 
 *Response*
 
-If successful, the value of `status` will be `ok` and the kicked user's session will be terminated and their user record removed. A message will be pushed to the room by `SYSTEM` to note that that user has been kicked and banned.
-
-If the requesting user lacks the privileges to kick a user, `SYSTEM` will push a message to warn that `user` tried to ban `tokick`.
-
-
-
-
-
-### kickUser
-
-Can only be called by the room admin, kicks a user out of the room (but allows them to return). Useful where you think a user's session has hung (for example)
-
-    {
-        "action":"kickUser",
-        "payload": {    
-                    "roomName": "[name of room]",
-                    "user": user,
-                    "kick": [user to kick],
-                    "sesskey": sessionkey
-        }
-    }
-
-*Response*
-
 If successful, the value of `status` will be `ok` and the kicked user's session will be terminated. A message will be pushed to the room by `SYSTEM` to note that that user has been kicked.
 
 If the requesting user lacks the privileges to kick a user, `SYSTEM` will push a message to warn that `user` tried to kick `tokick`.
 
 
 
-
-
 ### leaveRoom
 
 Used to leave the current room
@@ -200,7 +196,6 @@
 If successful, the value of `status` will be `ok`. Client's should then disable any automated message polling they are running.
 
 
-    
 
 ### pollMsg
 
@@ -239,16 +234,16 @@
 
 
 
-
-### sendMsg
-
-Used to send a message to the entire room
-
-    {
-        "action":"sendMsg",
+### sendDirectMsg
+
+Used to send a message to a specific user within the room. The message will not be visible to other room occupants.
+
+    {
+        "action":"sendDirectMsg",
         "payload": {    
                     "roomName": "[name of room]",
                     "msg": "[message payload]",
+                    "to": recipient
                     "user": user,
                     "sesskey": sessionkey
         }
@@ -275,17 +270,15 @@
 
 
 
-
-### sendDirectMsg
-
-Used to send a message to a specific user within the room. The message will not be visible to other room occupants.
-
-    {
-        "action":"sendDirectMsg",
+### sendMsg
+
+Used to send a message to the entire room
+
+    {
+        "action":"sendMsg",
         "payload": {    
                     "roomName": "[name of room]",
                     "msg": "[message payload]",
-                    "to": recipient
                     "user": user,
                     "sesskey": sessionkey
         }
@@ -313,5 +306,7 @@
 
 
 
+
+