[uefi-secure-boot-guide] master: Don't say we it doesn't protect against malware, because that's what it does. (bcbdbb9)

[sparks at fedoraproject.org]

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

On branch  : master

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

commit bcbdbb922260d26854382df8c9ee53f254651a24
Author: Peter Jones <pjones at redhat.com>
Date:   Wed Feb 27 15:12:16 2013 -0500

    Don't say we it doesn't protect against malware, because that's what it does.
    
    Instead explain that it only protects against one particular class of
    malware, and not others.
    
    Signed-off-by: Peter Jones <pjones at redhat.com>
    Signed-off-by: Eric Christensen <sparks at redhat.com>


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

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

diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 76d1a40..a1b292b 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -506,11 +506,11 @@ configuration on disk.)
         <section id="sect-UEFI_Secure_Boot_Guide-What_is_Secure_Boot-Risks">
                 <title>Potential Secure Boot Risks</title>
                 <para>
-			Secure Boot will not protect your PC from malware or attackers.
-Secure Boot itself protects the boot phase of a system. In &PRODUCT; if you
-use Secure Boot, what modules the kernel loads can be restricted, but user
-space malware cannot. The initial ramdisk (initrd) disk image used during
-boot is not signed and could contain malicious code. The kernel
+			Secure Boot will not protect your PC from most malware or attackers.
+Secure Boot itself protects the boot phase of a system, but does not protect against attacks against your running system or data.  In &PRODUCT; if you
+use Secure Boot, what modules the kernel loads can be restricted, but no
+additional protection is provide against user space malware. The initial ramdisk (initrd) disk image used during
+boot is not protected by this feature, and could contain malicious code.
                 </para>
 			<section id="sect-UEFI_Secure_Boot_Guide-What_is_Secure_Boot-Risks-Forced_Removal_of_Features">
 				<title>Forced removal of features in Secure Boot mode</title>