Minor doc tweaks, mostly white space

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

diff --git a/addrcheck/docs/ac-manual.xml b/addrcheck/docs/ac-manual.xml
index d5108d031b8bb4e8b25df19bf80be635b0b01869..ff3b4ffdde386a3e128e0c158ac1ebece29c20b3 100644 (file)
--- a/addrcheck/docs/ac-manual.xml
+++ b/addrcheck/docs/ac-manual.xml
@@ -49,9 +49,8 @@ Addrcheck can detect the following errors:</para>
 
 
 <para>Rather than duplicate much of the Memcheck docs here, 
-users of Addrcheck are
-advised to read <xref linkend="mc-manual.bugs"/>.  Some important
-points:</para>
+users of Addrcheck are advised to read <xref linkend="mc-manual.bugs"/>.  
+Some important points:</para>
 
 <itemizedlist>
 

diff --git a/cachegrind/docs/cg-manual.xml b/cachegrind/docs/cg-manual.xml
index 52f630098facc2d0b00b0fc25b3caaf9e78e7e3c..5b3f4796816896766c134eaf1caf30cbdb5598e0 100644 (file)
--- a/cachegrind/docs/cg-manual.xml
+++ b/cachegrind/docs/cg-manual.xml
@@ -289,11 +289,9 @@ file:</para>
 </itemizedlist>
 
 <para>The <computeroutput>.pid</computeroutput> suffix
-on the output file name 
-serves
-two purposes.  Firstly, it means you don't have to rename old log
-files that you don't want to overwrite.  Secondly, and more
-importantly, it allows correct profiling with the
+on the output file name serves two purposes.  Firstly, it means you 
+don't have to rename old log files that you don't want to overwrite.  
+Secondly, and more importantly, it allows correct profiling with the
 <computeroutput>--trace-children=yes</computeroutput> option of
 programs that spawn child processes.</para>
 

diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index 226eaacfd2cda89c40e644b2ce55c2e51447cee6..ae761485db1d743f4a43279c226703a6e6b18b2c 100644 (file)
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -124,11 +124,9 @@ Memcheck can detect the following problems:</para>
     that memory is not immediately made available for
     re-allocation.  Instead it is marked inaccessible and placed
     in a queue of freed blocks.  The purpose is to defer 
-    as long as possible
-    the
-    point at which freed-up memory comes back into circulation.
-    This increases the chance that Memcheck will be able to
-    detect invalid accesses to blocks for some significant period
+    as long as possible the point at which freed-up memory comes back 
+    into circulation.  This increases the chance that Memcheck will be 
+    able to detect invalid accesses to blocks for some significant period
     of time after they have been freed.</para>
     <para>This flag specifies the maximum total size, in bytes,
     of the blocks in the queue.  The default value is five million
@@ -145,11 +143,10 @@ Memcheck can detect the following problems:</para>
     distance below the stack pointer are due to bugs in gcc
     2.96, and does not report them.  The "small distance" is 256
     bytes by default.  Note that gcc 2.96 is the default compiler
-    on some older Linux distributions (RedHat 7.X)
-    and so you may need to use this flag.  Do not use it if
-    you do not have to, as it can cause real errors to be
-    overlooked.  A better alternative is to use a more recent gcc/g++ in which
-    this bug is fixed.</para>
+    on some older Linux distributions (RedHat 7.X) and so you may need to use 
+    this flag.  Do not use it if you do not have to, as it can cause real errors 
+    to be overlooked.  A better alternative is to use a more recent gcc/g++ in 
+    which this bug is fixed.</para>
   </listitem>
 
   <listitem id="partial">