Index: general/sysutils/which.xml
===================================================================
--- general/sysutils/which.xml	(revision 273653c1fc8885828e7abfb90836518aea6e0020)
+++ general/sysutils/which.xml	(revision 697e6ca5501521cc06dbb1ae2eacc1cfb0820d02)
@@ -25,22 +25,27 @@
   <title>Which-&which-version; and Alternatives</title>
 
+  <para>
+    The presence or absence of the <command>which</command> program in the
+    main LFS book is probably one of the most contentious issues on the
+    mailing lists. It has resulted in at least one flame war in the past. To
+    hopefully put an end to this once and for all, presented here are two
+    options for equipping your system with <command>which</command>. The
+    question of which <quote><command>which</command></quote> is for you to
+    decide.
+  </para>
+
   <indexterm zone="which">
     <primary sortas="a-Which">Which</primary>
   </indexterm>
 
-  <para>The presence or absence of the <command>which</command> program
-  in the main LFS book is probably one of the most contentious issues on the
-  mailing lists. It has resulted in at least one flame war in the past. To hopefully
-  put an end to this once and for all, presented here are two options for equipping
-  your system with <command>which</command>. The question of which
-  <quote><command>which</command></quote> is for you to decide.</para>
+  <sect2 role="package">
+    <title>Introduction to GNU Which</title>
 
-  <para>The first option is to install the actual GNU
-  <application>which</application> package.</para>
+    <para>
+      The first option is to install the actual GNU
+      <application>which</application> package.
+    </para>
 
-  &lfs82_checked;
-
-  <sect2 role="package">
-    <title>Introduction to Which</title>
+    &lfs82_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
Index: multimedia/libdriv/id3lib.xml
===================================================================
--- multimedia/libdriv/id3lib.xml	(revision 273653c1fc8885828e7abfb90836518aea6e0020)
+++ multimedia/libdriv/id3lib.xml	(revision 697e6ca5501521cc06dbb1ae2eacc1cfb0820d02)
@@ -32,4 +32,6 @@
     <para><application>id3lib</application> is a library for reading,
     writing and manipulating id3v1 and id3v2 multimedia data containers.</para>
+
+    &lfs82_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -85,5 +87,5 @@
 make</userinput></screen>
 
-    <para>This packages does not come wiht a working test suite.</para>
+    <para>This packages does not come with a working test suite.</para>
 
     <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
Index: postlfs/security/make-ca.xml
===================================================================
--- postlfs/security/make-ca.xml	(revision 273653c1fc8885828e7abfb90836518aea6e0020)
+++ postlfs/security/make-ca.xml	(revision 697e6ca5501521cc06dbb1ae2eacc1cfb0820d02)
@@ -15,5 +15,5 @@
 ]>
 
-<sect1 id="make-ca" xreflabel="make-ca">
+<sect1 id="make-ca" xreflabel="make-ca-&make-ca-version;">
   <?dbhtml filename="make-ca.html"?>
 
@@ -23,26 +23,5 @@
   </sect1info>
 
-  <title>make-ca</title>
-
-  <para>Public Key Infrastructure (PKI) is a method to validate the
-  authenticity of an otherwise unknown entity across untrusted networks. PKI
-  works by establishing a chain of trust, rather than trusting each individual
-  host or entity explicitly. In order for a certificate presented by a remote
-  entity to be trusted, that certificate must present a complete chain of
-  certificates that can be validated using the root certificate of a
-  Certificate Authority (CA) that is trusted by the local machine.</para>
-  
-  <para>Establishing trust with a CA involves validating things like company
-  address, ownership, contact information, etc., and ensuring that the CA has
-  followed best practices, such as undergoing periodic security audits by
-  independent investigators and maintaining an always available certificate
-  revocation list. This is well outside the scope of BLFS (as it is for most
-  Linux distributions). The certificate store provided here is taken from the
-  Mozilla Foundation, who have established very strict inclusion policies
-  described
-  <ulink url="https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/">here</ulink>.</para>
-
-  &lfs82_checked;
-
+  <title>make-ca-&make-ca-version;</title>
   <indexterm zone="make-ca">
     <primary sortas="a-make-ca">make-ca</primary>
@@ -52,5 +31,29 @@
     <title>Introduction to make-ca</title>
 
-   <bridgehead renderas="sect3">Package Information</bridgehead>
+    <para>
+      Public Key Infrastructure (PKI) is a method to validate the authenticity
+      of an otherwise unknown entity across untrusted networks. PKI works by
+      establishing a chain of trust, rather than trusting each individual host
+      or entity explicitly. In order for a certificate presented by a remote
+      entity to be trusted, that certificate must present a complete chain of
+      certificates that can be validated using the root certificate of a
+      Certificate Authority (CA) that is trusted by the local machine.
+    </para>
+  
+    <para>
+      Establishing trust with a CA involves validating things like company
+      address, ownership, contact information, etc., and ensuring that the CA
+      has followed best practices, such as undergoing periodic security audits
+      by independent investigators and maintaining an always available
+      certificate revocation list. This is well outside the scope of BLFS (as
+      it is for most Linux distributions). The certificate store provided here
+      is taken from the Mozilla Foundation, who have established very strict
+      inclusion policies described <ulink
+        url="https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/">here</ulink>.
+    </para>
+
+  &lfs82_checked;
+
+    <bridgehead renderas="sect3">Package Information</bridgehead>
     <itemizedlist spacing="compact">
       <listitem>
