supported subarches.
*version_stamp*::
-The version stamp is an identifier for the build. It can be anything
-you wish it to be, but it is usually a date (example: `2006.1`).
+The version stamp is an identifier for the build. It can be anything,
+but something date-like is recommended (example: `2006.1`).
*target*::
-The target specifies what target we want catalyst to do (example:
-`stage3`). Possible targets are:
+The target specifies what target we want catalyst to build (example:
+`stage3`). Supported targets are:
include::targets.generated.txt[tabsize=4]
(example: `2006.1`).
*source_subpath*::
-This specifies where the seed stage comes from for this target
+This specifies where the seed stage for this target comes from
(example: `default/stage3-x86-2006.1`). The path is relative to
`$storedir/builds`. The `rel_type` is also used as a path prefix for
the seed.
This allows the optional directory containing the output packages for
catalyst (example: `/tmp/packages`). Mainly used as a way for
different spec files to access the same cache directory. Default
-behavior is for this location to be autogenerated under `$storedir`
+behavior for this location is to be autogenerated under `$storedir`
based on the spec file.
*kerncache_path*::