[multiboot-guide] master: Please don't say 'UEFI BIOS' (367d089)

immanetize at fedoraproject.org immanetize at fedoraproject.org
Tue Jan 6 03:39:20 UTC 2015


Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git

On branch  : master

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

commit 367d089208fcc958c11d4d799759072c6b10a539
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Nov 1 14:34:05 2014 -0600

    Please don't say 'UEFI BIOS'
    
    These are two different things.  Using the terms incorrectly will just
    confuse people.


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

 en-US/BOOT-BIOS_or_UEFI.xml |    7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/en-US/BOOT-BIOS_or_UEFI.xml b/en-US/BOOT-BIOS_or_UEFI.xml
index 92b565c..b30dd83 100644
--- a/en-US/BOOT-BIOS_or_UEFI.xml
+++ b/en-US/BOOT-BIOS_or_UEFI.xml
@@ -32,12 +32,15 @@
       </para>
     </listitem>
   </itemizedlist>
-  <note>
+  <important>
     <title>The term <literal>BIOS</literal> is still used with UEFI systems</title>
     <para>
       Because BIOS systems have been around for so long, the term <literal>BIOS</literal> is often used to describe UEFI systems as well. Manufacturers might list system firmware updates as <literal>BIOS updates</literal> or provide directions to <literal>enter the BIOS setup menu</literal>.  The word has come to represent the pre-OS menu on your computer as much as the actual software, but your system may still be UEFI capable.
     </para>
-  </note>
+    <para>
+      To avoid confusion, this guide uses the term <literal>firmware</literal> when describing interactions with BIOS or UEFI menus.
+    </para>
+  </important>
   <itemizedlist>
     <title>Identifying a UEFI system</title>
     <listitem>



More information about the docs-commits mailing list