diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index d5f7a99..defce78 100644
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -69,11 +69,13 @@
     outer/.../bin/valgrind --sim-hints=enable-outer --trace-children=yes  \
        --tool=cachegrind -v inner/.../bin/valgrind --tool=none -v prog
 
-If you omit the --trace-children=yes, you'll only valgrind inner's launcher
-program, not its stage2.  The whole thing is fragile, confusing and slow,
-but it does work well enough for you to get some useful performance data.
-The inner Valgrind has most of its output (ie. those lines beginning with
-"==<pid>==") prefixed with a '>', which helps a lot.
+If you omit the --trace-children=yes, you'll only monitor inner's launcher
+program, not its stage2.
+
+The whole thing is fragile, confusing and slow, but it does work well enough
+for you to get some useful performance data.  The inner Valgrind has most of
+its output (ie. those lines beginning with "==<pid>==") prefixed with a '>',
+which helps a lot.
 
 At the time of writing the allocator is not annotated with client requests
 so Memcheck is not as useful as it could be.  It also has not been tested