# HG changeset patch
# User Paul Crowley <paul@lshift.net>
# Date 1255604086 -3600
# Node ID 3bff97f72a33b6376686ea86d199563e1b951ad4
# Parent  45dac87ae794233124bc73433b011b7fbfd281c2
ssh:// is the start of a URI

diff -r 45dac87ae794 -r 3bff97f72a33 doc/manual.docbook
--- a/doc/manual.docbook	Thu Oct 15 11:53:14 2009 +0100
+++ b/doc/manual.docbook	Thu Oct 15 11:54:46 2009 +0100
@@ -123,7 +123,7 @@
 jay@my-workstation:~/hgadmin$ </computeroutput></screen>
 <para>
 Sam can now read and write to your
-<literal>ssh://hg@repository-host/repository/name</literal> repository.
+<uri>ssh://hg@repository-host/repository/name</uri> repository.
 Most other changes to access control can be made simply by making and
 pushing changes to <filename
 class='directory'>hgadmin</filename>, and you can use Mercurial to
@@ -437,7 +437,7 @@
 All of the repositories controlled by mercurial-server are owned by a
 single user, the <systemitem
 class="username">hg</systemitem> user, which is why all URLs for
-mercurial-server repositories start with <literal>ssh://hg@...</literal>.
+mercurial-server repositories start with <uri>ssh://hg@...</uri>.
 Each SSH key that has access to the repository has an entry in
 <filename>~hg/.ssh/authorized_keys</filename>; this is how the SSH daemon
 knows to give that key access. When the user connects over SSH, their