Be consistent in the naming of sections describing command-line options.
Also, use "option" rather than "flag" where possible, for consistency.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10758 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index 8454f2e..9ee8ea3 100644
--- a/docs/xml/FAQ.xml
+++ b/docs/xml/FAQ.xml
@@ -132,7 +132,7 @@
older glibc versions causes this crash.</para>
<para>Workaround for 1.1.X and later versions of Valgrind: use the
- <option>--run-libc-freeres=no</option> flag. You may then get space
+ <option>--run-libc-freeres=no</option> option. You may then get space
leak reports for glibc allocations (please don't report these to
the glibc people, since they are not real leaks), but at least the
program runs.</para>
@@ -424,7 +424,7 @@
<para>If you are tracing large trees of processes, it can be less
disruptive to have the output sent over the network. Give Valgrind
- the flag <option>--log-socket=127.0.0.1:12345</option> (if you want
+ the option <option>--log-socket=127.0.0.1:12345</option> (if you want
logging output sent to port <literal>12345</literal> on
<literal>localhost</literal>). You can use the valgrind-listener
program to listen on that port:</para>
@@ -557,7 +557,7 @@
<answer id="a-undeferrors">
<para>Prior to version 3.4.0, the answer was "we don't know how to do it
without huge performance penalties". As of 3.4.0, try using the
- <option>--track-origins=yes</option> flag. It will run slower than
+ <option>--track-origins=yes</option> option. It will run slower than
usual, but will give you extra information about the origin of
uninitialised values.</para>