# HG changeset patch
# User Matti Hamalainen <ccr@tnsp.org>
# Date 1366242555 -10800
# Node ID c9f2913b933a7d30f1875a362b1d76741ba0aa06
# Parent  b2c4d5d9bed85373b4e285a191f1ea04a0e43f1a
Fix some link tags.

diff -r b2c4d5d9bed8 -r c9f2913b933a docs/manual.sgml
--- a/docs/manual.sgml	Thu Apr 18 02:42:52 2013 +0300
+++ b/docs/manual.sgml	Thu Apr 18 02:49:15 2013 +0300
@@ -457,7 +457,7 @@
 <para>
 If you are using Windows, and wish to use the development version, you
 can use the regular Mercurial command line client, or a GUI interface
-such as <ulink linkend="http://tortoisehg.bitbucket.org/">TortoiseHg</ulink>.
+such as <ulink url="http://tortoisehg.bitbucket.org/">TortoiseHg</ulink>.
 </para>
 
 <para>
@@ -506,7 +506,7 @@
 
 <section id="intro-upgrading-from-svn"><title>Upgrading from Subversion repo to Mercurial</title>
 <para>
-Previously we used <ulink linkend="">Subversion</ulink> as our version
+Previously we used <emphasis>Subversion</emphasis> as our version
 control system, before migrating to Mercurial. If you have used the svn
 version, you can switch by deleting or renaming the old checkout working
 directory of Subversion. For example, if you have local changes, you can do:
@@ -3161,7 +3161,7 @@
 If you have prepared a fix for some bug or a new feature, you can send us a patch.
 <emphasis>A changeset patch made against current Mercurial repository head/tip is highly preferred</emphasis>,
 short instructions on how to do that can be found below. You will probably need to refer to
-<ulink linkend="http://mercurial.selenic.com/guide/">Mercurial guide</ulink> for generic
+<ulink url="http://mercurial.selenic.com/guide/">Mercurial guide</ulink> for generic
 Mercurial usage instructions and how to set it up. For making proper commits, you'll need to
 at the very least set up your username, etc.
 </para>