[uefi-secure-boot-guide] f18.4: Fix typos (d0b1430)

[sparks at fedoraproject.org]

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

On branch  : f18.4

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

commit d0b1430c4d3c2a1e297f5effb58b7be52b814497
Author: Yuri Chornoivan <yurchor at ukr.net>
Date:   Tue Mar 12 08:18:22 2013 +0200

    Fix typos
    
    Signed-off-by: Eric Christensen <sparks at fedoraproject.org>


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

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

diff --git a/en-US/System_Configuration.xml b/en-US/System_Configuration.xml
index 1afd920..bc58d36 100644
--- a/en-US/System_Configuration.xml
+++ b/en-US/System_Configuration.xml
@@ -9,7 +9,7 @@
 This chapter describes how to configure systems for use with UEFI
 Secure Boot.  The required steps vary from system to system because
 they depend on how the firmware implements the UEFI specification, but
-the descriptions should give you an idea where to look
+the descriptions should give you an idea where to look.
 </para>
 <warning>
 <title>System can become unbootable</title>
@@ -333,7 +333,7 @@ disabled.
 UEFI Secure Boot (and its Microsoft variant) require secure firmware
 updates.  Typically, this is implemented by writing a signed update to
 a staging area, where the firmware picks it up during the next boot,
-verifies it, and then proceeds to overwrite the actual firmwre.
+verifies it, and then proceeds to overwrite the actual firmware.
 However, this process is still far from foolproof and firmware updates
 still can make devices unusable, requiring a firmware replacement.
 </para>
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 86eedd1..5ca5c08 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -506,7 +506,7 @@ boot is not protected by this feature, and could contain malicious code.
 				<title>Forced removal of features in Secure Boot mode</title>
 			<para>
 We currently use a blacklist approach to disable known-unsafe kernel
-functionality.  In some cases, specific funcionality has been disabled.  In
+functionality.  In some cases, specific functionality has been disabled.  In
 most cases such functionality is obscure and seldom used.  Currently, the
 list of restricted functionality includes: 
 </para>