From 9499f8bc3ff935c507c2d7fc36d5debb6949b89d Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 4 Jun 2020 10:34:56 +0200 Subject: spec: Rename required in mandatory attributes The term "required" is quite overloaded in the specification context. Use "mandatory" instead. Shorten the phrase "explicitly defined attributes" to "explicit attributes". --- spec/spec/build-config-header.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'spec/spec/build-config-header.yml') diff --git a/spec/spec/build-config-header.yml b/spec/spec/build-config-header.yml index 98a332a2..647f847c 100644 --- a/spec/spec/build-config-header.yml +++ b/spec/spec/build-config-header.yml @@ -35,7 +35,7 @@ spec-info: written to the configuration header file during the configure command execution. To have all configuration defines from sibling items available it is recommended to link them in the proper order. - required-attributes: all + mandatory-attributes: all spec-name: Build Configuration Header Item Type spec-type: build-config-header type: spec -- cgit v1.2.3