From dbed35e657fe3ddcffa8c1ded8544da786218a41 Mon Sep 17 00:00:00 2001 From: Angelos Evripiotis Date: Sun, 11 Feb 2018 13:30:17 +0000 Subject: projectconf.rst: clarify 'type option' Reword 'Flags type options' slightly for more clarity. We use 'option type' to refer to these thingies elsewhere, adjust 'arch' to be the same way. --- doc/source/projectconf.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/projectconf.rst b/doc/source/projectconf.rst index 9af52d65a..ead949c6c 100644 --- a/doc/source/projectconf.rst +++ b/doc/source/projectconf.rst @@ -369,7 +369,7 @@ need not be specified and will default to an empty set. **Evaluating** -Flags type options can be tested in conditional expressions using +Options of type ``flags`` can be tested in conditional expressions using a pythonic *in* syntax to test if an element is present in a set: .. code:: yaml @@ -389,7 +389,7 @@ exported as a comma separated list of selected value strings. Architecture ~~~~~~~~~~~~ -The ``arch`` type option is special enumeration option which +The ``arch`` option type is special enumeration option which defaults to the result of `uname -m`, and does not support assigning any default in the project configuration. -- cgit v1.2.1