Fix three typos.

[lopsub.git] / lopsub-suite.5.m4

diff --git a/lopsub-suite.5.m4 b/lopsub-suite.5.m4
index d453c9c9d844dffb64c194ac84dceaa08ef5f1aa..0244c38a49f056f086476c3e3238a61241e698a3 100644 (file)
--- a/lopsub-suite.5.m4
+++ b/lopsub-suite.5.m4
@@ -64,7 +64,7 @@ See the section on command directives below.
 
 Supercommands and subcommands share the same set of possible command
 directives. They differ mainly in the way the documentation is
-formated. There can only be one supercommand but arbitrary many
+formatted. There can only be one supercommand but arbitrary many
 subcommands. For example, the supercommand could be the name of
 the application, and the subcommands could be "load", "save" "info"
 and "quit". The subcommand would be passed as the first non-option
@@ -305,6 +305,12 @@ only given in the config file. The recommended way to deal with
 this situation is to parse command line and config file separately,
 then merge the two parse results and check in the application if the
 option is given in the merged parse result.
+
+There is another disadvantage of this flag: if the parser fails due
+to a missing option that was declared required, it is not possible to
+detect if other options were given. For example, if the suite defines
+the --help option, and the application is executed with this option
+only, the parser will still return a parse error.
 .B
 .IP ignored
 This flag indicates that the current option is in fact not a real option.
@@ -333,8 +339,8 @@ The syntax for the array of values is
 For each option for which the
 .B values
 directive was specified, the lopsubgen command generates a C
-enumeration which contains the given identifiers. This allows to
-refer to each possible value through a numeric constant.
+enumeration which contains the given identifiers. This allows
+referring to each possible value through a numeric constant.
 .TP
 .B default_val
 This directive makes only sense for options which take an argument. For