Fix use of "command line X" in binutils doc

[deliverable/binutils-gdb.git] / gprof / gprof.texi

diff --git a/gprof/gprof.texi b/gprof/gprof.texi
index bdcda00c4e016618cce14d62bbaf74135117fb07..456805b687d61847c8252d5af2dbf259a55b971f 100644 (file)
--- a/gprof/gprof.texi
+++ b/gprof/gprof.texi
@@ -331,7 +331,7 @@ initialised.  This is usually detected by the program encountering a
 segmentation fault as soon as it is run.  The solution is to link
 against a static version of the library containing the profiling
 support code, which for @code{gcc} users can be done via the
-@samp{-static} or @samp{-static-libgcc} command line option.  For
+@samp{-static} or @samp{-static-libgcc} command-line option.  For
 example:
 
 @example
@@ -357,7 +357,7 @@ there is still support for displaying this kind of information in
 @code{gprof}. @xref{Line-by-line, ,Line-by-line Profiling}.
 
 It also worth noting that @code{gcc} implements a
-@samp{-finstrument-functions} command line option which will insert
+@samp{-finstrument-functions} command-line option which will insert
 calls to special user supplied instrumentation routines at the entry
 and exit of every function in their program.  This can be used to
 implement an alternative profiling scheme.
@@ -1431,7 +1431,7 @@ With the older versions of @code{gcc} the program usually has to be
 compiled with a @samp{-g} option, in addition to @samp{-pg}, in order
 to generate debugging symbols for tracking source code lines.
 Note, in much older versions of @code{gcc} the program had to be
-compiled with the @samp{-a} command line option as well.
+compiled with the @samp{-a} command-line option as well.
 
 The flat profile is the most useful output table
 in line-by-line mode.