gdb/doc: Consistency fixes for GDB/MI documentation
authorAndrew Burgess <aburgess@redhat.com>
Thu, 16 Feb 2023 09:22:43 +0000 (09:22 +0000)
committerAndrew Burgess <aburgess@redhat.com>
Mon, 20 Feb 2023 14:18:03 +0000 (14:18 +0000)
commita5b6347b660df23259737ec3fc4a2f3a97f31b14
tree7f2db6520b5893a7b2932b5658f9b86d802efd2a
parentc9802aca6d152c4a47252f69ad81556dbc24e312
gdb/doc: Consistency fixes for GDB/MI documentation

I noticed two inconsistencies in the GDB/MI documentation, which this
commit addresses:

  1. Each MI command is introduced like this:

     @subheading The @code{-command-name} Command

     Except for a few of the tracing command, which just use:

     @subheading -command-name

     In this commit I've updated all these trace commands to use the
     more common format.

  2. Each MI command starts with a @subheading, and then the details
     of that command are split up using multiple @subsubheading
     entries.

     Except for a few commands which use @subheading for the top-level
     command, and then continue to use @subheading for each part of
     the command description.

     In this commit I've updated these to use @subsubheading where
     appropriate.
gdb/doc/gdb.texinfo