Fix broken links in the manual. Bug #113190.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4778

diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index db21da9baa38e1439090626856eba64d4cbe8379..f8b8c129fa6adab691a3dd1a73674d00eb6bcce3 100644 (file)
--- a/docs/xml/FAQ.xml
+++ b/docs/xml/FAQ.xml
@@ -10,7 +10,7 @@
   <releaseinfo>August 2005</releaseinfo>
   <author>
     <surname>
-      <ulink url="http://www.valgrind.org/www/developers.html">Valgrind Developers</ulink>
+      <ulink url="http://www.valgrind.org/info/developers.html">Valgrind Developers</ulink>
     </surname>
     <affiliation><orgname>
       <ulink url="mailto:&vg-vemail;">&vg-vemail;</ulink>
@@ -404,7 +404,7 @@ valgrind-listener 12345
 </programlisting>
 
   <para>Obviously you have to start the listener process first.
-  See the Manual: <ulink url="http://www.valgrind.org/docs/bookset/manual-core.out2file.html">Directing output to file</ulink> for more details.</para>
+  See the manual for more details.</para>
 
   <para>Second, if your program is statically linked, most Valgrind tools
   won't work as well, because they won't be able to replace certain
@@ -481,8 +481,7 @@ int main(void)
   "still reachable", and "suppressed"?</para>
  </question>
  <answer>
-  <para>The details are in the Manual: 
-   <ulink url="http://www.valgrind.org/docs/bookset/mc-manual.leaks.html">Memory leak detection</ulink>.</para>
+  <para>The details are in the Memcheck section of the user manual.</para>
 
   <para>In short:</para>
    <itemizedlist>

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index a2e40c0c6416c3d0682e12866c43a812edaffa30..f7c60e0a72025ca9d061f13cdb5997c38296dd74 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1597,7 +1597,7 @@ effect before dying in this way.  This is a known problem which
 we should fix.</para>
 
 <para>Read the 
-<ulink url="http://www.valgrind.org/docs/faq/index.html">FAQ</ulink> for
+<ulink url="http://www.valgrind.org/docs/FAQ/">FAQ</ulink> for
 more advice about common problems, crashes, etc.</para>
 
 </sect1>