From 63f82da63d7d7dc3b1e26992cd9dd66b16c804b8 Mon Sep 17 00:00:00 2001
From: Nicholas Nethercote <njn@valgrind.org>
Date: Mon, 25 Jul 2005 23:30:24 +0000
Subject: [PATCH] fix breakage/wibbles

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4261
---
 cachegrind/docs/cg-manual.xml | 2 +-
 memcheck/docs/mc-manual.xml   | 5 ++---
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/cachegrind/docs/cg-manual.xml b/cachegrind/docs/cg-manual.xml
index 35b55eb0a..88b93e807 100644
--- a/cachegrind/docs/cg-manual.xml
+++ b/cachegrind/docs/cg-manual.xml
@@ -35,7 +35,7 @@ misses.  In particular, it records:</para>
   </listitem>
 </itemizedlist>
 
-<para>On a modern x86 machine, an L1 miss will typically cost
+<para>On a modern machine, an L1 miss will typically cost
 around 10 cycles, and an L2 miss can cost as much as 200
 cycles. Detailed cache profiling can be very useful for improving
 the performance of your program.</para>
diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index 744255b02..ba0ea3c90 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -61,9 +61,8 @@ Memcheck can detect the following problems:</para>
 
 <itemizedlist id="leakcheck">
   <listitem>
-    <para><computeroutput>--leak-check=no</computeroutput>
-    <para><computeroutput>--leak-check=summary</computeroutput>
-    [default]</para>
+    <para><computeroutput>--leak-check=no</computeroutput></para>
+    <para><computeroutput>--leak-check=summary</computeroutput> [default]</para>
     <para><computeroutput>--leak-check=full</computeroutput></para>
     <para>When enabled, search for memory leaks when the client
     program finishes.  A memory leak means a malloc'd block,