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
/etc/mke2fs.conf contains the default value of
various command line options of mke2fs. 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
ext4 file system with
metadata_csum_seed 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 @@
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 dhcpcd, is
not normally appropriate for a server and wireless_tools,
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/ldNext 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 --host
+ since glibc will always use those relating to the --host
parameter passed to its configure script; e.g., in our case, the compiler
will be $LFS_TGT-gcc and the readelf
tool will be $LFS_TGT-readelf. The kernel headers can