docs/BOOT_LOADER_INTERFACE: minor grammar fixes

This commit is contained in:
Zbigniew Jędrzejewski-Szmek
2025-05-06 21:04:00 +02:00
parent f72e277d0b
commit 2fe7cdd91a

View File

@@ -52,7 +52,7 @@ variables. All EFI variables use the vendor UUID
be used to let the OS know which boot menu entries were discovered by the
boot loader. A boot loader entry identifier should be a short, non-empty
alphanumeric string (possibly containing `-`, too). The list should be in the
order the entries are shown on screen during boot. See below regarding a
order the entries are shown on screen during boot. See below regarding the
recommended vocabulary for boot loader entry identifiers.
* The EFI variable `LoaderEntryDefault` contains the default boot loader entry
@@ -62,13 +62,13 @@ variables. All EFI variables use the vendor UUID
used in case of a system failure. System failure (SysFail) boot entries can
optionally modify the automatic selection order in the event of a failure,
such as a boot firmware update failure with the failure status recorded in
the EFI system table. If a system failure occurs and `LoaderEntrySysFail` is set,
systemd-boot will use this boot entry and store the actual SysFail reason in
the `LoaderSysFailReason` EFI variable.
the EFI system table. If a system failure occurs and `LoaderEntrySysFail` is
set, systemd-boot will use this boot entry, and store the actual SysFail
reason in the `LoaderSysFailReason` EFI variable.
* The EFI variable `LoaderSysFailReason` contains the system failure reason.
This variable is used in cooperation with `LoaderEntrySysFail` boot entry.
If system failure doesn't occur `LoaderSysFailReason` is not set at all.
If system failure doesn't occur, `LoaderSysFailReason` is not set.
* Similarly, the EFI variable `LoaderEntryOneShot` contains the default boot
loader entry to use for a single following boot. It is set by the OS in order