docs: improve description of secure attribute for loader element

The original text was not explaining what this attribute actually
controls and could have been interpreted as a control switch for the
Secure boot feature in firmwares.

Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index a2ea2690a5cc7c0a84911c265ed8b1a6e13a4fa1..70709ef9467c361c99d98af446536abf37f142ba 100644 (file)
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -167,7 +167,9 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
    in the guest memory the file should be mapped. For instance, if the loader
    path points to an UEFI image, ``type`` should be ``pflash``. Moreover, some
    firmwares may implement the Secure boot feature. Attribute ``secure`` can be
-   used then to control it. :since:`Since 2.1.0`
+   used to tell the hypervisor that the firmware is capable of Secure Boot feature.
+   It cannot be used to enable or disable the feature itself in the firmware.
+   :since:`Since 2.1.0`
 ``nvram``
    Some UEFI firmwares may want to use a non-volatile memory to store some
    variables. In the host, this is represented as a file and the absolute path