# HG changeset patch
# User Paul Crowley <paul@lshift.net>
# Date 1255606060 -3600
# Node ID 475a05ed5f0ea5312370d1b17b294e242e0c501f
# Parent  72cb7a42650aa32c4f1fe9480d0a80957f8650d9
Sam's machine is called saucer

diff -r 72cb7a42650a -r 475a05ed5f0e doc/manual.docbook
--- a/doc/manual.docbook	Thu Oct 15 12:21:04 2009 +0100
+++ b/doc/manual.docbook	Thu Oct 15 12:27:40 2009 +0100
@@ -99,7 +99,7 @@
 At this stage, no-one but you has any access to any repositories you
 create on this system. In order to give anyone else access, you'll need a
 copy of their SSH public key; we'll assume you have that key in
-<filename>~/sam-key.pub</filename>.  To manage access, you make changes to the special <filename
+<filename>~/sam-saucer-key.pub</filename>.  To manage access, you make changes to the special <filename
 class='directory'>hgadmin</filename> repository.
 </para>
 <screen><computeroutput>jay@spoon:~$ </computeroutput><userinput>hg clone ssh://hg@jeeves/hgadmin</userinput>
@@ -109,9 +109,9 @@
 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
 jay@spoon:~$ </computeroutput><userinput>cd hgadmin</userinput>
 <computeroutput>jay@spoon:~/hgadmin$ </computeroutput><userinput>mkdir -p keys/users/sam</userinput>
-<computeroutput>jay@spoon:~/hgadmin$ </computeroutput><userinput>cp ~/sam-key.pub keys/users/sam/their-workstation</userinput>
+<computeroutput>jay@spoon:~/hgadmin$ </computeroutput><userinput>cp ~/sam-saucer-key.pub keys/users/sam/saucer</userinput>
 <computeroutput>jay@spoon:~/hgadmin$ </computeroutput><userinput>hg add</userinput>
-<computeroutput>adding keys/users/sam/their-workstation
+<computeroutput>adding keys/users/sam/saucer
 jay@spoon:~/hgadmin$ </computeroutput><userinput>hg commit -m "Add Sam's key'"</userinput>
 <computeroutput>jay@spoon:~/hgadmin$ </computeroutput><userinput>hg push</userinput>
 <computeroutput>pushing to ssh://hg@jeeves/hgadmin