summaryrefslogtreecommitdiff
path: root/Documentation/security
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/security')
-rw-r--r--Documentation/security/vboot/index.md2
-rw-r--r--Documentation/security/vboot/list_vboot.md2
-rw-r--r--Documentation/security/vboot/measured_boot.md4
3 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/security/vboot/index.md b/Documentation/security/vboot/index.md
index ff2261a669..faa8cb8561 100644
--- a/Documentation/security/vboot/index.md
+++ b/Documentation/security/vboot/index.md
@@ -196,7 +196,7 @@ not into the read/write coreboot file systems in *FW_MAIN_A* and *FW_MAIN_B*.
**VBOOT_ENABLE_CBFS_FALLBACK**
Normally coreboot will use the active read/write coreboot file system for all
-of it's file access when VBOOT is active and is not in recovery mode.
+of it's file access when vboot is active and is not in recovery mode.
When the `VBOOT_ENABLE_CBFS_FALLBACK` option is enabled the cbfs file system will
first try to locate a file in the active read/write file system. If the file
diff --git a/Documentation/security/vboot/list_vboot.md b/Documentation/security/vboot/list_vboot.md
index 1bef8234be..6b41597f18 100644
--- a/Documentation/security/vboot/list_vboot.md
+++ b/Documentation/security/vboot/list_vboot.md
@@ -1,4 +1,4 @@
-# VBOOT enabled devices
+# vboot-enabled devices
## Emulation
- QEMU x86 i440fx/piix4 (aka qemu -M pc)
diff --git a/Documentation/security/vboot/measured_boot.md b/Documentation/security/vboot/measured_boot.md
index 45d66dd2d2..df4cc68008 100644
--- a/Documentation/security/vboot/measured_boot.md
+++ b/Documentation/security/vboot/measured_boot.md
@@ -120,12 +120,12 @@ PCR-7 are left empty.
### PCR-0
_Hash:_ SHA1
-_Description:_ Google VBoot GBB flags.
+_Description:_ Google vboot GBB flags.
### PCR-1
_Hash:_ SHA1/SHA256
-_Description:_ Google VBoot GBB HWID.
+_Description:_ Google vboot GBB HWID.
### PCR-2
_Hash:_ SHA1/SHA256