diff -r e99262dfa950 -r 731a72b742db README
--- a/README	Thu May 28 10:43:30 2009 +0100
+++ b/README	Tue Oct 13 15:30:03 2009 +0100
@@ -4,7 +4,7 @@
 you choose, identified by ssh keys, with easy key and access management
 based on hg.
 
-http://hg.opensource.lshift.net/mercurial-server/
+http://www.lshift.net/mercurial-server.html
 
 Copyright (C) 2008-2009 LShift Ltd.
 
@@ -40,7 +40,7 @@
 
 To give a user access to the repository, place their key in an
 appropriately-named subdirectory of "/etc/mercurial-server/keys" and run
-"/usr/local/lib/mercurial-server/refresh-auth". You can then control what
+"/usr/local/share/mercurial-server/refresh-auth". You can then control what
 access they have to what repositories by editing the control file
 "/etc/mercurial-server/access.conf", which can match the names of these keys
 against a glob pattern. 
@@ -75,7 +75,7 @@
 (ie the file is called something like
 "/etc/mercurial-server/keys/root/yourname/yourhostname") so that you can
 easily manage users who have a different key on each host they use. Then run
-"/usr/local/lib/mercurial-server/refresh-auth".
+"/usr/local/share/mercurial-server/refresh-auth".
 
 The repository is now ready to use, and you are now the sole user able to
 change and create repositories on this repository host.  
@@ -98,7 +98,7 @@
 "keys/users" subdirectory - these users will be able to read and write to any
 repository (except one - see below) but will not be able to create new
 repositories. As always, when you change "/etc/mercurial-server/keys" you need
-to re-run "/usr/local/lib/mercurial-server/refresh-auth".
+to re-run "/usr/local/share/mercurial-server/refresh-auth".
 
 LOGGING
 
@@ -151,4 +151,5 @@
 Thanks for reading this far. If you use mercurial-server, please tell me about
 it.
 
-Paul Crowley, 2009
+Paul Crowley, paul@lshift.net, 2009
+