[uefi-secure-boot-guide] master: Fixed a couple of spelling errors (3a643fd)

[sparks at fedoraproject.org]

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

On branch  : master

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

commit 3a643fdcacca7183d9b9d656140a070a5b0fcdfd
Author: Eric Christensen <sparks at redhat.com>
Date:   Thu Jan 31 11:37:54 2013 -0500

    Fixed a couple of spelling errors


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

 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 49c7b7f..e87d0cf 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -26,7 +26,7 @@ outside of the concept of Secure Boot and into another topic.
 		</para>
 		<para>
 		Fedora has expanded the chain of trust into the Kernel.
-Verification happens as far as only loadin signed kernel modules, but it
+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
 initrd cannot currently be signed, it cannot be verified.
@@ -36,7 +36,7 @@ initrd cannot currently be signed, it cannot be verified.
                 <title>What does Secure Boot not protect you from?</title>
                 <para>
 			Secure Boot will not protect your PC from malware or attackers.
-Secure Boot itslef is simply to protect the boot phase of a system. In
+Secure Boot itself is simply to protect the boot phase of a system. In
 Fedora if you use Secure Boot, what modules the kernel loads can be
 restricted, but user space malware cannot. This of course doesn't mean
 Secure Boot isn't useful, just that it currently only serves a single