Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit 4d18f6767a9b73b9919c0f47fbddacf55ae61c8d
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:15 2013 -0500
Fix a minor gramatical problem.
Subject and verb plurality should match.
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 9dfc8a3..2cb46da 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -482,8 +482,8 @@ see <xref
linkend="sect-UEFI_Secure_Boot_Guide-What_is_Secure_Boot-Microsoft_Imp
into the kernel. Verification happens before loading kernel modules,
but it does not extend to user space applications. We can be certain
that no unsigned executable code is present until the initial ramdisk
-(initrd) is loaded. Since initrd contents is not cryptographically
-signed and contains executable code, booting a signed &PRODUCT; boot
+(initrd) is loaded. Since initrd contents are not cryptographically
+signed and contain executable code, booting a signed &PRODUCT; boot
loader can eventually lead to arbitrary effects.
</para>
<para>