Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit 95f0d20dba099dde9221d38972f810154c997b73
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:04 2013 -0500
Nobody calls Secure Boot "Verified Boot".
I think "Verified Boot" is intended as a category here, so make it read
that way.
Signed-off-by: Peter Jones <pjones(a)redhat.com>
Signed-off-by: Eric Christensen <sparks(a)redhat.com>
---------------------------------------------------------------
en-US/What_is_Secure_Boot.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 90a23c2..0a65ad3 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -14,8 +14,8 @@ potentially, user space, it is possible to prevent the execution of
unsigned code.
</para>
<para>
- Secure Boot is sometimes called <firstterm>Verified
- Boot</firstterm>. Boot path validation is also part of other
+ <firstterm>Secure Boot</firstterm> is a form of <firstterm>Verified
+ Booting</firstterm>. Boot path validation is also part of other
technologies such as <firstterm>Trusted Boot</firstterm>. Boot path
validation is indepedent of secure storage of cryptographic keys and
remote attestation.