anchor.diff:  ----
   
   === Header and Footer
  -The `header` will be shown at the top of the usage help message (before the synopsis). The first header line is also the line shown in the subcommand list if your command has subcommands (see <<usage-help-for-subcommands>>).
  +The `header` will be shown at the top of the usage help message (before the synopsis). The first header line is also the line shown in the subcommand list if your command has subcommands (see <<Usage Help for Subcommands>>).
   
   Use the `footer` attribute to specify one or more lines to show below the generated usage help message.
   Each element of the attribute String array is displayed on a separate line.
   
  -The `headerHeading` and `footerHeading` may contain format specifiers. See <<compact-example>>.
  +The `headerHeading` and `footerHeading` may contain format specifiers. See <<Compact Example>>.
   
   
   === Abbreviated Synopsis
  
positive.code: ----
  
  The usage help message for each subcommand is produced by calling `CommandLine.usage(new SubCommand(), out)`.
  For example, see <<section-headings>> for an example subcommand (`git-commit`), which produces the help message shown
  in <<expanded-example>>.
  
  == Subclassing for Reuse
  Picocli will walk the class hierarchy to check for annotations, so you can declare common @Options and @Command attributes on a superclass and override these fields or attributes on a subclass.
  
negative.code:                                 multiple -m options are given, their values are
                                  concatenated as separate paragraphs.
  ----
  The annotated class that this usage help message is generated from is shown in <<Section Headings>>.
  
  == Help API
  For further customization, picocli has a Help API.
  