[uefi-secure-boot-guide] master: Changed wording around 'malware' being present (5917d3b)

[sparks at fedoraproject.org]

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

On branch  : master

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

commit 5917d3bd34dff2e8bcf7b372403c15a2f5246875
Author: Eric Christensen <sparks at redhat.com>
Date:   Thu Jan 31 14:15:34 2013 -0500

    Changed wording around 'malware' being present


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

 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>