[lfs] branch trunk updated: English grammar fixes

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <173347595435.5321.5535577273019484484@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new c87106896 English grammar fixes
c87106896 is described below

commit c87106896ce3cfa4e7a1751240400318b8dd7fb7
Author: Xi Ruoyao <[email protected]>
AuthorDate: Fri Dec 6 17:05:02 2024 +0800

    English grammar fixes
    
    Suggested-by: †KJM† <[email protected]>
---
 chapter08/e2fsprogs.xml           | 2 +-
 chapter11/afterlfs.xml            | 2 +-
 part3intro/toolchaintechnotes.xml | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/chapter08/e2fsprogs.xml b/chapter08/e2fsprogs.xml
index c5718c191..d99922610 100644
--- a/chapter08/e2fsprogs.xml
+++ b/chapter08/e2fsprogs.xml
@@ -146,7 +146,7 @@ install-info --dir-file=/usr/share/info/dir /usr/share/info/com_err.info</userin
     <para>
       <filename>/etc/mke2fs.conf</filename> contains the default value of
       various command line options of <command>mke2fs</command>.  You may
-      edit the file to make the default values suitable for your need.
+      edit the file to make the default values suitable for your needs.
       For example, some utilities (not in LFS or BLFS) cannot recognize a
       <systemitem class='filesystem'>ext4</systemitem> file system with
       <literal>metadata_csum_seed</literal> feature enabled.
diff --git a/chapter11/afterlfs.xml b/chapter11/afterlfs.xml
index 88a3c0114..bfd6b084f 100644
--- a/chapter11/afterlfs.xml
+++ b/chapter11/afterlfs.xml
@@ -54,7 +54,7 @@
      <para>
         In addition to the above, there is a set of applications for system
         management for all kinds of systems. These applications are all in the
-        BLFS book. Not all packages are needed in every environments. For
+        BLFS book. Not all packages are needed in every environment. For
         example <ulink url="&blfs-book;basicnet/dhcpcd.html">dhcpcd</ulink>, is
         not normally appropriate for a server and <ulink
         url="&blfs-book;basicnet/wireless_tools.html">wireless_tools</ulink>,
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index 3714596fc..1dad94103 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -360,7 +360,7 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     <para>Next comes glibc. The most important
     considerations for building glibc are the compiler, binary tools, and
     kernel headers. The compiler and binary tools are generally not an issue
-    since glibc will always those relating to the <parameter>--host</parameter>
+    since glibc will always use those relating to the <parameter>--host</parameter>
     parameter passed to its configure script; e.g., in our case, the compiler
     will be <command>$LFS_TGT-gcc</command> and the <command>readelf</command>
     tool will be <command>$LFS_TGT-readelf</command>. The kernel headers can

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.