From 477ef25e67b1a5b769d6704f29bbecabbe9363dc Mon Sep 17 00:00:00 2001
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Tue, 15 Aug 2017 23:30:46 +0200
Subject: [PATCH]  Small improvement to user manual: capitalise another
 occurence of memcheck

   (yes, I am experimenting with valgrind git repository :)
---
 docs/xml/manual-core.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index c88bffe4ee..4cd26a5200 100644
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1728,7 +1728,7 @@ Massif, Helgrind, DRD), the following options apply.</para>
         For massif and helgrind, specifying <varname>full</varname>
         implies to capture a stack trace for each free operation,
         while normally these tools only capture an allocation stack
-        trace.  For memcheck, the cpu overhead for the
+        trace.  For Memcheck, the cpu overhead for the
         value <varname>full</varname> is small, as this can only be
         used in combination with
         <option>--keep-stacktraces=alloc-and-free</option> or
-- 
2.47.2