[uefi-secure-boot-guide] master: Made some editing and spelling changes (0ab487b)

[sparks at fedoraproject.org]

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

On branch  : master

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

commit 0ab487b3c4f0491c6dd4bd9e7109529c17ce804a
Author: Eric Christensen <sparks at fedoraproject.org>
Date:   Fri Feb 1 17:49:43 2013 -0500

    Made some editing and spelling changes


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

 en-US/Tools.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/en-US/Tools.xml b/en-US/Tools.xml
index c9d6854..dd567b4 100644
--- a/en-US/Tools.xml
+++ b/en-US/Tools.xml
@@ -6,18 +6,18 @@
 <chapter id="chap-UEFI_Secure_Boot_Guide-Tools">
 	<title>Tools</title>
 	<para>
-		Several tools have been developed to allow &PRODUCT; work with the UEFI Secure Boot firmware.
+		Several tools have been developed to allow &PRODUCT; to work with the UEFI Secure Boot firmware.
 	</para>
 	<section id="sect-UEFI_Secure_Boot_Guide-Tools-shim">
 		<title>Shim</title>
 		<para>
-			<firstterm>Shim</firstterm> is the cryptographically signed software that creates the trust between the UEFI firmware and GRUB and the kernel software.  Shim is cryptographically signed by Verisign (via Microsoft) so that the UEFI firmware will cryptographically recognize the &PRODUCT; system and allow the software to continue through the boot process.  The shim validates GRUB and kernel though a cryptographic verification based on a &PRODUCT; key used to sign all three.
+			Shim is the cryptographically signed software that creates the trust between the UEFI firmware and GRUB and the kernel software.  Shim is cryptographically signed by Verisign (via Microsoft) so that the UEFI firmware will cryptographically recognize the &PRODUCT; system and allow the software to continue through the boot process.  The shim validates GRUB and kernel through a cryptographic verification based on a &PRODUCT; key used to sign all three.
 		</para>
 	</section>
         <section id="sect-UEFI_Secure_Boot_Guide-Tools-pesign">
-                <title>pesign</title>
+                <title>Pesign</title>
                 <para>
-			<firstterm>Pesign</firstterm> allows users to create their own shim and use their own cryptographic keys.  Using this tool, one can create their own trust model and not be required to trust the Microsoft keys and trust model.  Once the user has created their keys and signed their shim, and optionally signed and built GRUB and kernel, they can use the setup mode in the firmware to install &PRODUCT; and use the <firstterm>sbsetup</firstterm> tool as provided by pesign to enroll their keys in the firmware.
+			<firstterm>Pesign</firstterm> allows users to create their own shim and use their own cryptographic keys.  Using this tool, one can create their own trust model and not be required to trust the Microsoft trust model.  Once the user has created their keys and signed their shim, and optionally signed and built GRUB and kernel, they can use the setup mode in the firmware to install &PRODUCT; and use the <firstterm>sbsetup</firstterm> tool as provided by pesign to enroll their keys in the firmware.
                 </para>
         </section>
         <section id="sect-UEFI_Secure_Boot_Guide-Tools-efikeygen">