Update hexchat.md

[irc/freenode/web-7.0.git] / content / kb / using / registration.md

diff --git a/content/kb/using/registration.md b/content/kb/using/registration.md
index 029c49677f861777470087062ecaa4d71027f23a..04f4162c153441d8289087869b5e9d6c3100e520 100755 (executable)
--- a/content/kb/using/registration.md
+++ b/content/kb/using/registration.md
@@ -1,7 +1,7 @@
 Title: Nickname Registration
 ---
 Your nick is how people on freenode know you. If you register it, you'll be able to use the same nick over and over. If you don't register, someone else may end
-up registering the nick you want. If you register and use the same nick, people will begin to know you by reputation. 
+up registering the nick you want. If you register and use the same nick, people will begin to know you by reputation.
 
 If a channel is set to mode +r, you won't be able to join it unless you are registered and identified to NickServ. If you try to join, you might be forwarded to
 a different channel. If a channel is set to quiet unregistered users (mode `+q $~a`), you won't be able to speak while on that channel unless you are registered
@@ -31,9 +31,9 @@ staff will be happy to discuss it and answer any questions you may have.
 3.  It's useful, but not required, to have an alternate nick grouped to your account. For example, if your primary nick is foo:
 
         /nick foo_
-    
+
     then identify to your primary account:
-    
+
         /msg NickServ IDENTIFY foo password
 
     and finally, group the new nick to your account
@@ -44,26 +44,23 @@ staff will be happy to discuss it and answer any questions you may have.
     gives you the benefit of having all your nicks covered by the same cloak, should you choose to wear a cloak. The exception to this is where you might want to
     run a bot. You should register a separate account for your bot.
 
-4.  Configure your client to identify itself to NickServ automatically whenever it connects to freenode so that it's less likely you'll connect to the network
-    without being identified to NickServ. The easiest approach is to specify your NickServ password as a server password.  If your client supports server
-    password, please set this up as accountname:password. Make sure to include the colon. This will allow you to identify to your services account on connect,
-    regardless of the nickname you are using when you connect. For example: /connect chat.freenode.net 6667 mquin:uwhY8wgzWw22-zXs.M39p
-
-
 Logging In
 ==========
 
 You'll need to log in to your nickname each time you reconnect to freenode.
 
-The simplest, and most robust, way to do this is to configure [SASL](/kb/using/sasl), if your client supports it. If not, you can supply your login details, in
-the form `<account>:<password>`, as a server password and they will be forwarded to NickServ when you finish connecting.
+The simplest, and most robust, way to do this is to configure [SASL](kb/using/sasl), if your client supports it. If not, you can supply your login details, in
+the form `<account>:<password>`, as a server password and they will be forwarded to NickServ when you finish connecting. For example:
+
+    /connect chat.freenode.net 6667 mquin:uwhY8wgzWw22-zXs.M39p
 
 Nickname Expiry
 ===============
 
 Registered nicknames and accounts will expire if they're not used for a long time, after which they'll be available for another user to take over. See our
-[policies](/pages/policies) for details of when this occurs.
+[policies](pages/policies) for details of when this occurs.
 
 While nicknames and accounts do not automatically get deleted when they expire -- only when another user requests to take over the registration -- we do
 occasionally perform clean-up runs on the services database, in which we will automatically drop all registrations which have been idle for a long time. When we
 do this, we set the threshold for deletion considerably higher than the documented expiry time, to ensure that users close to the limit do not lose out.
+