diff --git a/chapter08/man-db.xml b/chapter08/man-db.xml
index 88c811d33..229111131 100644
--- a/chapter08/man-db.xml
+++ b/chapter08/man-db.xml
@@ -113,11 +113,7 @@
 
     <para>To test the results, issue:</para>
 
-<screen><userinput remap="test">make -k check</userinput></screen>
-
-    <!-- https://gitlab.com/man-db/man-db/-/issues/25 -->
-    <para>One test named <filename>man1/lexgrog.1</filename> is known
-    to fail.</para>
+<screen><userinput remap="test">make check</userinput></screen>
 
     <para>Install the package:</para>
 
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml
index 7104d9cba..13d79cfdd 100644
--- a/chapter08/pkgmgt.xml
+++ b/chapter08/pkgmgt.xml
@@ -69,6 +69,17 @@
         it.  </para>
       </listitem>
 
+      <listitem>
+        <para>Reinstalling the same version of Glibc (&glibc-version; for
+        this release of LFS) with patches should be safe when these patches
+        do not change ABI and API.  When a security vulnerability is found
+        in Glibc, we often need to apply such a patch to fix the
+        vulnerability and reinstall Glibc.  Consult
+        <ulink url='&lfs-root;lfs/advisories/'>LFS security
+        advisories</ulink> if you are alerted for a published Glibc security
+        vulnerability but unsure about the action to take.</para>
+      </listitem>
+
       <listitem> <para>If a package containing a shared library is updated, and
       if the name of the library changes, then any packages dynamically
       linked to the library must be recompiled, to link against the