nailing-cargo knows about `update`, `generate-lockfile` and
`fetch`; all other subcommands are (silently) treated the same way
as `build` (ie, no subcommand properties). See
- [`--subcommand-props`](#subcommand_props) for more detail about how the
+ `--subcommand-props` for more detail about how the
subcommand affects nailing-cargo's behaviour.
The default is to use the cargo subcommand found from parsing
subcommand you are running - especially for out-of-tree builds.
nailing-cargo only has a short builtin list of commands it knows
about (see [`-s<subcommand`](#s_subcommand)). For other commands, you may need to
- add an entry to `@subcmd_propss` in the source, or use
+ add an entry to `@subcmd_props` in the source, or use
[`--subcommand-props`](#subcommand_props).
* Out of tree builds require a unified filesystem view: eg, different