Fix mention of defunct unban command. Resolves #2337

docs/source/Banning.md

@@ -3,7 +3,7 @@
 
 Whether due to abuse, blatant breaking of your rules, or some other reason, you will eventually find
 no other recourse but to kick out a particularly troublesome player. The default command set has
-admin tools to handle this, primarily `@ban`, `@unban`, and `@boot`.
+admin tools to handle this, primarily `ban`, `unban`, and `boot`.
 
 ## Creating a ban
 
@@ -16,7 +16,7 @@ have tried to be nice. Now you just want this troll gone.
 
 The easiest recourse is to block the account YouSuck from ever connecting again.
 
-     @ban YouSuck
+     ban YouSuck
 
 This will lock the name YouSuck (as well as 'yousuck' and any other capitalization combination), and
 next time they try to log in with this name the server will not let them!
@@ -24,12 +24,12 @@ next time they try to log in with this name the server will not let them!
 You can also give a reason so you remember later why this was a good thing (the banned account will
 never see this)
 
-     @ban YouSuck:This is just a troll.
+     ban YouSuck:This is just a troll.
 
 If you are sure this is just a spam account, you might even consider deleting the player account
 outright:
 
-     @delaccount YouSuck
+     account/delete YouSuck
 
 Generally, banning the name is the easier and safer way to stop the use of an account -- if you
 change your mind you can always remove the block later whereas a deletion is permanent.
@@ -49,7 +49,7 @@ the `who` command, which will show you something like this:
 The "Host" bit is the IP address from which the account is connecting. Use this to define the ban
 instead of the name:
 
-     @ban 237.333.0.223
+     ban 237.333.0.223
 
 This will stop YouSuckMore connecting from their computer. Note however that IP address might change
 easily - either due to how the player's Internet Service Provider operates or by the user simply
@@ -58,7 +58,7 @@ groups of three digits in the address. So if you figure out that !YouSuckMore ma
 237.333.0.223, 237.333.0.225, and 237.333.0.256 (only changes in their subnet), it might be an idea
 to put down a ban like this to include any number in that subnet:
 
-     @ban 237.333.0.*
+     ban 237.333.0.*
 
 You should combine the IP ban with a name-ban too of course, so the account YouSuckMore is truly
 locked regardless of where they connect from.
@@ -71,16 +71,16 @@ blocking out innocent players who just happen to connect from the same subnet as
 YouSuck is not really noticing all this banning yet though - and won't until having logged out and
 trying to log back in again. Let's help the troll along.
 
-     @boot YouSuck
+     boot YouSuck
 
 Good riddance. You can give a reason for booting too (to be echoed to the player before getting
 kicked out).
 
-     @boot YouSuck:Go troll somewhere else.
+     boot YouSuck:Go troll somewhere else.
 
 ### Lifting a ban
 
-Use the `@unban` (or `@ban`) command without any arguments and you will see a list of all currently
+Use the `unban` (or `ban`) command without any arguments and you will see a list of all currently
 active bans:
 
     Active bans
@@ -90,7 +90,7 @@ active bans:
 
 Use the `id` from this list to find out which ban to lift.
 
-     @unban 2
+     unban 2
       
     Cleared ban 2: 237.333.0.*
 
@@ -132,7 +132,7 @@ case) the lock to fail.
 - **type thomas = FlowerPot** -- Turn an annoying player into a flower pot (assuming you have a
 `FlowerPot` typeclass ready)
 - **userpassword thomas = fooBarFoo** -- Change a user's password
-- **delaccount thomas** -- Delete a player account (not recommended, use **ban** instead)
+- **account/delete thomas** -- Delete a player account (not recommended, use **ban** instead)
 
 - **server** -- Show server statistics, such as CPU load, memory usage, and how many objects are
 cached