[system-administrators-guide] Changing entities

stephenw stephenw at fedoraproject.org
Sat Dec 13 08:55:24 UTC 2014


commit 1a4a51331cac15726a7b97b72161253e21d04096
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Sat Dec 13 09:52:39 2014 +0100

    Changing entities

 en-US/Working_with_the_GRUB_2_Boot_Loader.xml |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
index 1e81667..45fe966 100644
--- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
+++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
@@ -845,10 +845,10 @@ For more information on adding kernel options, see <xref linkend="sec-Editing_an
 			<section id="sec-UEFI_Secure_Boot_Support_in_Fedora">
 				<title>UEFI Secure Boot Support in Fedora</title>
 				<para>
-					&PRODUCT; includes support for the UEFI Secure Boot feature, which means that &PRODUCT; can be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems with the Secure Boot technology enabled, all drivers that are loaded must be signed with a valid certificate, otherwise the system will not accept them. All drivers provided by Red&nbsp;Hat are signed by the UEFI CA certificate.
+					&MAJOROS; includes support for the UEFI Secure Boot feature, which means that &MAJOROS; can be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems with the Secure Boot technology enabled, all drivers that are loaded must be signed with a valid certificate, otherwise the system will not accept them. All drivers provided by Red&nbsp;Hat are signed by the UEFI CA certificate.
 				</para>
-				<para>			 
-					If you want to load externally built drivers &mdash; drivers that are not provided on the &PRODUCT;&nbsp;Linux DVD &mdash; you must make sure these drivers are signed as well.
+				<para>
+					If you want to load externally built drivers &mdash; drivers that are not provided on the &MAJOROS;&nbsp;Linux DVD &mdash; you must make sure these drivers are signed as well.
 				</para>
 				<para>
 				 <!--Information on signing custom drivers is available in <xref linkend="sect-signing-kernel-modules-for-secure-boot" />.-->


More information about the docs-commits mailing list