From 02c49ffe60a232e2f0b16cc973a909a6ad2ae263 Mon Sep 17 00:00:00 2001 From: Kristian Heljas <11139388+kristianheljas@users.noreply.github.com> Date: Thu, 2 Mar 2023 20:46:02 +0200 Subject: [PATCH] Encourage true/false for module documentation (#80060) Co-authored-by: Felix Fontein --- docs/docsite/rst/dev_guide/developing_modules_documenting.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst index f459e43326f..e7b5c2d5fb6 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst @@ -162,8 +162,8 @@ All fields in the ``DOCUMENTATION`` block are lower-case. All fields are require * If ``required`` is false/missing, ``default`` may be specified (assumed 'null' if missing). * Ensure that the default value in the docs matches the default value in the code. * The default field must not be listed as part of the description, unless it requires additional information or conditions. - * If the option is a boolean value, you can use any of the boolean values recognized by Ansible: - (such as true/false or yes/no). Choose the one that reads better in the context of the option. + * If the option is a boolean value, you can use any of the boolean values recognized by Ansible + (such as ``true``/``false`` or ``yes``/``no``). Document booleans as ``true``/``false`` for consistency and compatibility with ansible-lint. :choices: