[uefi-secure-boot-guide] master: Merge branch 'master' of git://git.fedorahosted.org/git/docs/uefi-secure-boot-guide into bressers (214fe04)

[sparks at fedoraproject.org]

Repository : http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git

On branch  : master

>---------------------------------------------------------------

commit 214fe046ccf287b27b125096a7c405bfc6fad7cb
Merge: 30a75a5 5917d3b
Author: Josh Bressers <josh at bress.net>
Date:   Thu Jan 31 13:36:34 2013 -0600

    Merge branch 'master' of git://git.fedorahosted.org/git/docs/uefi-secure-boot-guide into bressers



>---------------------------------------------------------------

 en-US/What_is_Secure_Boot.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 1cb0b84..b13206e 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -28,7 +28,7 @@ outside of the concept of Secure Boot and into another topic.
 		&PRODUCT; has expanded the chain of trust into the Kernel.
 Verification happens as far as only loading signed kernel modules, but it
 does not extend to user space applications. We can be certain that no
-malware is present until the initial ramdisk (initrd) is loaded. Since
+unsigned executable code is present until the initial ramdisk (initrd) is loaded. Since
 initrd cannot currently be signed, it cannot be verified.
 		</para>
 	</section>