diff --git a/introduction/important/pkgmgt.xml b/introduction/important/pkgmgt.xml
index f4222486e8..1309ebc184 100644
--- a/introduction/important/pkgmgt.xml
+++ b/introduction/important/pkgmgt.xml
@@ -2,15 +2,15 @@
 <?dbhtml filename="pkgmgt.html" dir="introduction"?>
 <title>Package Management</title>
 
-<para>Package Management has been one of the often requested addition
+<para>Package Management is an often requested addition
 to the <acronym>LFS</acronym> Book. A Package Manager allows tracking
 the installation of files making it easy to remove and upgrade packages.
 And before you begin to wonder, NO - this section does not talk about any
 particular package manager, nor does it recommend one. What it provides is
 a roundup of the more popular techniques and how they work. The perfect
 package manager for you may be among these techniques or may be a combination
-of two or more of these techniques. This section also mentions
-in brief about some upgrade issues.</para>
+of two or more of these techniques. This section briefly mentions
+issues that may arise when upgrading packages.</para>
 
 <para>Some reasons why no package manager is mentioned in <acronym>LFS</acronym>
 or <acronym>BLFS</acronym>:</para>
@@ -31,14 +31,14 @@ to find if one of them fits your need.</para>
 <title>Upgrade Issues</title>
 
 <para>Following are some points that you should be aware of when upgrading
-pacakges, especially on a running system.</para>
+packages, especially on a running system.</para>
 
 <itemizedlist>
 <listitem><para>It is recommended that if one of the toolchain package (glibc, gcc,
 binutils) needs to be upgraded to a newer minor vesion, it is safer to rebuild
-<acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by by
+<acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by
 rebuilding all the packages in their dependency order. We do not recommend the
-latter. For example if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
+latter. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
 to rebuild. For micro version updates, a simple reinstallation usually works, but
 is not guaranteed. For example, upgrading from glibc-2.3.1 to glibc-2.3.2 will not
 usually cause any problems.</para></listitem>
@@ -68,7 +68,7 @@ is already loaded in memory.</para></listitem>
 <para>The following are some common package management techniques.</para>
 
 <sect3>
-<title>Its all in my head!</title>
+<title>It is all in my head!</title>
 
 <para>Yes, this is a package management technique. Some folks do not find the
 need for a package manager because they know the packages intimately and know
@@ -108,7 +108,7 @@ Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
 
 <para>The installation needs to be faked, so that the package thinks that it is
 installed in <filename>/usr</filename> though in reality it is installed in
-<filename>/ust/pkg</filename> hierachy. Installing in this manner is not usually a trivial
+<filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
 task. For example, consider that you are installing a package libfoo-1.1. The following
 instructions may not install the package properly:</para>
 
@@ -153,7 +153,7 @@ reliable if two packages are being installed on two different consoles.</para>
 <sect3>
 <title>LD_PRELOAD based</title>
 
-<para>In this approach, a library is preloaded before installation and during
+<para>In this approach, a library is preloaded before installation. During
 installation, this library tracks the packages that are being installed by
 attaching itself to various executables such as <command>cp</command>,
 <command>install</command>, <command>mv</command> and tracking the system