Changeset c8391c3d

Timestamp:

09/20/2022 03:45:30 AM (19 months ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal

Children:

4afbfbd

Parents:

ea11b87

git-author:

Pierre Labastie <pierre.labastie@…> (09/20/2022 03:40:16 AM)

git-committer:

Pierre Labastie <pierre.labastie@…> (09/20/2022 03:45:30 AM)

Message:

Spelling and grammar fixes to grub-setup

From the file attached to
https://wiki.linuxfromscratch.org/blfs/ticket/17085
by D Bryant.

File:

• postlfs/filesystems/uefi-bootloaders/grub-setup.xml (modified) (23 diffs)

postlfs/filesystems/uefi-bootloaders/grub-setup.xml

@@ -20 +20 @@
     <para>
       BLFS does not have the essential packages to support Secure Boot. To
-      set up the boot process with GRUB for UEFI installed in BLFS, Secure
+      set up the boot process with GRUB and UEFI in BLFS, Secure
       Boot must be turned off from the configuration interface of the
       firmware.  Read the documentation provided by the manufacturer of your
@@ -99 +99 @@
 
     <para>
-      Now the USB flash drive can be used as a emergency boot disk on x86-64
+      Now the USB flash drive can be used as an emergency boot disk on any x86-64
       UEFI platform.  It will boot the system and show the GRUB shell.  Then you
-      can type commands to boot your operating systems on the hard drive.
+      can type commands to boot your operating system from the hard drive.
       To learn how to select the boot device, read the manual of your
       motherboard or laptop.
@@ -142 +142 @@
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>The meaning of the configuration options:</title>
 
       <varlistentry>
@@ -172 +172 @@
         <listitem>
           <para>The combination of these options allows the kernel to
-          print debug messages (along with Tux logos) at the early stage of
-          the boot process with UEFI.  To ensure them functional at the early
-          stage, they shouldn't be built as a kernel module unless an
+          print debug messages (along with Tux logos) at an early stage of
+          the boot process with UEFI.  To ensure they are functional at that early
+          stage, they shouldn't be built as kernel modules unless an
           initramfs will be used.</para>
         </listitem>
@@ -187 +187 @@
 
     <para>
-      On EFI based system, the bootloaders are installed in a special FAT32
+      On EFI based systems, the bootloaders are installed in a special FAT32
       partition called an <emphasis>EFI System Partition</emphasis> (ESP).
-      If your system supports EFI, and a recent version of Linux
+      If your system supports EFI, and a recent version of some Linux
       distribution or Windows is pre-installed, it's likely that the ESP
-      is already created.  As the
+      has already been created.  As the
       <systemitem class="username">root</systemitem> user, list all the
       partitions on your hard drive (replace <userinput>sda</userinput>
@@ -205 +205 @@
 
     <para>
-      If the system or the hard drive is new, or it's a first time
-      install an UEFI booted OS on the system, the ESP may not exist.
+      If the system or the hard drive is new, or it's the first
+      installation of a UEFI-booted OS on the system, the ESP may not exist.
       In that case, create a new partition, make a
       <systemitem class="filesystem">vfat</systemitem> file system on it,
@@ -215 +215 @@
     <warning>
       <para>
-        Some (old) UEFI implementations may demand the ESP to be the first
+        Some (old) UEFI implementations may require the ESP to be the first
         partition on the disk.
       </para>
@@ -252 +252 @@
       <filename>EFI/BOOT/BOOTX64.EFI</filename>.  Normally, a boot loader
       should be installed into a custom path and the path should be recorded
-      into the EFI variables.  The use of the hardcoded path should be
-      avoided as much as possible.  However, in some cases we have to use
+      in the EFI variables.  The use of the hardcoded path should be
+      avoided if possible.  However, in some cases we have to use
       the hardcoded path:
     </para>
@@ -260 +260 @@
       <listitem>
         <para>
-          The system is not booted with EFI yet, causing EFI variables
+          The system is not booted with EFI yet, making EFI variables
           inaccessible.
         </para>
@@ -266 +266 @@
       <listitem>
         <para>
-          The EFI firmware is 64-bit but the LFS system is 32-bit, causing
+          The EFI firmware is 64-bit but the LFS system is 32-bit, making
           EFI variables inaccessible because the kernel cannot invoke EFI
           runtime services with a different virtual address length.
@@ -273 +273 @@
       <listitem>
         <para>
-          LFS is built for a Live USB, so we cannot rely on EFI variables
-          which is stored in NVRAM or EEPROM on the local machine.
+          LFS is built for a Live USB, so we cannot rely on EFI variables,
+          which are stored in NVRAM or EEPROM on the local machine.
         </para>
       </listitem>
       <listitem>
         <para>
-          You are unable or unwilling to install
+          You are unable or unwilling to install the
           <application>efibootmgr</application> for manipulating boot
           entries in EFI variables.
@@ -287 +287 @@
 
     <para>
-      In these cases, follow this section to install GRUB EFI
+      In these cases, follow these instructions to install the GRUB EFI
       application into the hardcoded path and make a minimal boot
-      configuration. Otherwise it's better to skip this section and read the
-      remaining sections to set up the boot configuration in a normal way.
-    </para>
-
-    <para>
-      To install GRUB with the EFI application installed into the hardcoded
+      configuration. Otherwise it's better to skip ahead and set up the
+      boot configuration normally.
+    </para>
+
+    <para>
+      To install GRUB with the EFI application in the hardcoded
       path <filename>EFI/BOOT/BOOTX64.EFI</filename>, first ensure the boot
       partition is mounted at <filename class="directory">/boot</filename>
-      and the ESP mounted at
-      <filename class="directory">/boot/efi</filename>.  Then as the &root;
+      and the ESP is mounted at
+      <filename class="directory">/boot/efi</filename>.  Then, as the &root;
       user, run the command:
     </para>
@@ -304 +304 @@
     <note>
       <para>
-        The command will overwrite
+        This command will overwrite
         <filename>/boot/efi/EFI/BOOT/BOOTX64.EFI</filename>.  It may break a
         bootloader already installed there.  Back it up if you are not sure.
@@ -313 +313 @@
 
     <para>
-      The command would install GRUB EFI application into the hardcoded path
+      This command will install the GRUB EFI application into the hardcoded path
       <filename>/boot/efi/EFI/BOOT/BOOTX64.EFI</filename>, so the EFI
       firmware can find and load it.  The remaining GRUB files are installed
-      into <filename class="directory">/boot/grub</filename> directory and
+      in the <filename class="directory">/boot/grub</filename> directory and
       will be loaded by <filename>BOOTX64.EFI</filename> during system boot.
     </para>
@@ -322 +322 @@
     <note>
       <para>
-        The EFI firmware usually prefers the EFI applications with the path
-        recorded in boot entries stored in EFI variables, to the EFI
+        The EFI firmware usually prefers the EFI applications with a path
+        stored in EFI variables to the EFI
         application at the hardcoded path.  So you may need to invoke the
         boot selection menu or firmware setting interface to select the
         newly installed GRUB manually on the next boot.  Read the manual of
-        your motherboard or laptop to figure out how.
+        your motherboard or laptop to learn how.
       </para>
     </note>
 
     <para>
-      If you've followed this section and set up a minimal boot
-      configuration, now skip until
+      If you've followed the instructions in this section and set up a minimal boot
+      configuration, now skip ahead to
       <quote>Creating the GRUB Configuration File</quote>.
     </para>
@@ -343 +343 @@
     <para>
       The installation of GRUB on a UEFI platform requires that the EFI Variable
-      file system, <systemitem class="filesystem">efivarfs</systemitem>, to be
+      file system, <systemitem class="filesystem">efivarfs</systemitem>, is
       mounted.  As the <systemitem class="username">root</systemitem> user,
       mount it if it's not already mounted:
@@ -354 +354 @@
         If the system is booted with UEFI and systemd,
         <systemitem class="filesystem">efivarfs</systemitem> will be mounted
-        automatically.  However in the LFS chroot environment it still needs to
+        automatically.  However, in the LFS chroot environment it still needs to
         be mounted manually.
       </para>
@@ -375 +375 @@
         <filename class="directory">/sys/firmware/efi</filename> will be
         missing. In this case you should boot the system in UEFI mode with
-        the emergency boot disk or minimal boot configuration created as
+        the emergency boot disk or using a minimal boot configuration created as
         above, then mount
         <systemitem class="filesystem">efivarfs</systemitem> and continue.
@@ -401 +401 @@
       GRUB-2.06) so it will not use much space in the ESP.  A typical ESP
       size is 100 MB (for Windows boot manager, which uses about 50 MB in
-      the ESP). Once <filename>grubx64.efi</filename> loaded by the
-      firmware, it will load GRUB modules in the boot partition.
+      the ESP). Once <filename>grubx64.efi</filename> has been loaded by the
+      firmware, it will load GRUB modules from the boot partition.
       The default location is
       <filename class="directory">/boot/grub</filename>.
@@ -424 +424 @@
 
     <para>
-      Issue <command>efibootmgr | cut -f 1</command> to recheck the EFI boot
+      Issue the <command>efibootmgr | cut -f 1</command> command to recheck the EFI boot
       configuration.  An example of the output is:
     </para>
@@ -485 +485 @@
     <para>
       <literal>(hd0,2)</literal>, <literal>sda2</literal>, and
-      <literal>5.19.2-lfs-11.2</literal> should be replaced to match your
+      <literal>5.19.2-lfs-11.2</literal> must match your
       configuration.
     </para>
@@ -491 +491 @@
     <note>
       <para>
-        From GRUB's perspective, the files are relative to the partition
-        are used. If you used a separate /boot partition, remove /boot from the
+        From GRUB's perspective, the files are relative to the partitions
+        used. If you used a separate /boot partition, remove /boot from the
         above paths (to kernel and to <filename>unicode.pf2</filename>). You
-        will also need to change the set root line to point to the boot
+        will also need to change the "set root" line to point to the boot
         partition.
       </para>
@@ -530 +530 @@
       in this case the Windows Boot Manager. You may put more usable tools
       in EFI executable format (for example, an EFI shell) into the ESP and
-      create GRUB entries for them.
+      create GRUB entries for them, as well.
     </para>