@@ -17,7 +17,7 @@ new command without understanding why or why not that instance is correct.
1717The :doc: `Human Interface Guide <humaninterfaceguide >`
1818describes the guildelines for option names and usage. In short:
1919 * All option names shall be GNU-style long names (two leading dashes).
20- * Some global options may have short nmaes , generally limited to those defined
20+ * Some global options may have short names , generally limited to those defined
2121 in support libraries such as ``cliff ``.
2222
2323General Command Options
@@ -36,7 +36,7 @@ prepended (such as in the traditional GNU option usage) like `--share` and
3636In order to handle those APIs that behave differently when a field is set to
3737`None ` and when the field is not present in a passed argument list or dict,
3838each of the boolean options shall set its own variable to `True ` as part of
39- a mutiually exclusive group, rather than the more common configuration of
39+ a mutually exclusive group, rather than the more common configuration of
4040setting a single destination variable `True ` or `False ` directly. This allows
4141us to detect the situation when neither option is present (both variables will
4242be `False `) and act accordingly for those APIs where this matters.
@@ -218,7 +218,7 @@ Some options have no default value and the API does not allow them to be
218218`None `, then these options are always required when users use the command
219219to which these options belong.
220220
221- Required options must be validated by the CLI to aviod omissions. The CLI
221+ Required options must be validated by the CLI to avoid omissions. The CLI
222222validation may provide an error message for the user if a required option
223223is not specified.
224224(for example: ``error: argument --test is required ``)
0 commit comments