diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml
index 15c27faeeb..400aeb5f59 100644
--- a/en_US.ISO8859-1/articles/releng/article.sgml
+++ b/en_US.ISO8859-1/articles/releng/article.sgml
@@ -75,8 +75,8 @@
     access was opened up to everyone on the Internet.  Therefore only
     a <quote>select</quote> group of nearly 300 people are given write
     access to the <acronym>CVS</acronym> repository.  These
-    <emphasis>committers[6]</emphasis> are responsible for the bulk of
-    FreeBSD development.  An elected <emphasis>core-team[7]</emphasis>
+    <emphasis>committers[5]</emphasis> are responsible for the bulk of
+    FreeBSD development.  An elected <emphasis>core-team[6]</emphasis>
     of very senior developers provides some level of direction over
     the project.</para>
 
@@ -94,7 +94,7 @@
     Both branches live in a master CVS repository in California and
     are replicated via <application
     class="software">CVSup</application>[2] to mirrors all over the
-    world.  FreeBSD-CURRENT[8] is the <quote>bleeding-edge</quote> of
+    world.  FreeBSD-CURRENT[7] is the <quote>bleeding-edge</quote> of
     FreeBSD development where all new changes first enter the system.
     FreeBSD-STABLE is the development branch from which major releases
     are made.  Changes go into this branch at a different pace, and
@@ -109,14 +109,14 @@
     widespread availability of binary release snapshots, and the
     tendency of our user community to keep up with -STABLE development
     with CVSup and <quote><command>make</command>
-    <maketarget>world</maketarget></quote>[8] helps to keep
+    <maketarget>world</maketarget></quote>[7] helps to keep
     FreeBSD-STABLE in a very reliable condition even before the
     quality assurance activities ramp up pending a major
     release.</para>
 
   <para>Bug reports and feature requests are continuously submitted by
     users throughout the release cycle.  Problems reports are entered into our
-    <application class="software">GNATS</application>[9] database
+    <application class="software">GNATS</application>[8] database
     through email, the &man.send-pr.1; application, or via the web
     interface provided at <ulink
     url="http://www.FreeBSD.org/send-pr.html"></ulink>.
@@ -396,7 +396,7 @@
 
       <para><application>Sysinstall</application> should be updated to note
         the number of available ports and the amount of disk space required
-	for the Ports Collection.  This information is currently kept in
+	for the Ports Collection[4].  This information is currently kept in
 	<filename>src/release/sysinstall/dist.c</filename>.</para>
 
       <para>After the release has been built, a number of file should
@@ -930,7 +930,7 @@
     <para>The FreeBSD system installation and configuration tool,
       &man.sysinstall.8;, can be scripted to provide automated installs
       for large sites. This functionality can be used in conjunction
-      with &intel; PXE[13] to bootstrap systems from the network, or
+      with &intel; PXE[12] to bootstrap systems from the network, or
       via custom boot floppies with a sysinstall script.  An example
       sysinstall script is available in the CVS tree as
       <filename>src/release/sysinstall/install.cfg</filename>.</para>
@@ -1003,7 +1003,7 @@
       <para><emphasis>Installation Tools</emphasis> - Our installation
         program has long since outlived its intended life span.
         Several projects are under development to provide a more
-        advanced installation mechanism.  The libh project[5] was one
+        advanced installation mechanism.  The libh project was one
         such project that aimed to provide an intelligent new package
         framework and GUI installation program.</para>
     </listitem>
@@ -1025,8 +1025,8 @@
     community.  I would also like to thank &a.rgrimes;, &a.phk;, and others
     who worked on the release engineering tools in the very early days
     of FreeBSD.  This article was influenced by release engineering
-    documents from the CSRG[14], the NetBSD Project[11], and John
-    Baldwin's proposed release engineering process notes[12].</para>
+    documents from the CSRG[13], the NetBSD Project[10], and John
+    Baldwin's proposed release engineering process notes[11].</para>
 </sect1>
 
 <!-- Reference / Biblio Section -->
@@ -1044,41 +1044,38 @@
   <para>[4] FreeBSD Ports Collection
   <ulink url="http://www.FreeBSD.org/ports"></ulink></para>
 
-  <para>[5] The libh Project
-  <ulink url="http://www.FreeBSD.org/projects/libh.html"></ulink></para>
-
-  <para>[6] FreeBSD Committers <ulink
+  <para>[5] FreeBSD Committers <ulink
   url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html"></ulink>
   </para>
 
-  <para>[7] FreeBSD Core-Team
+  <para>[6] FreeBSD Core-Team
   <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/staff-core.html"></ulink></para>
 
-  <para>[8] FreeBSD Handbook
+  <para>[7] FreeBSD Handbook
   <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook"></ulink>
   </para>
 
-  <para>[9] GNATS: The GNU Bug Tracking System
+  <para>[8] GNATS: The GNU Bug Tracking System
   <ulink url="http://www.gnu.org/software/gnats"></ulink>
   </para>
 
-  <para>[10] FreeBSD PR Statistics
+  <para>[9] FreeBSD PR Statistics
   <ulink url="http://www.FreeBSD.org/prstats/index.html"></ulink></para>
 
-  <para>[11] NetBSD Developer Documentation: Release Engineering
+  <para>[10] NetBSD Developer Documentation: Release Engineering
   <ulink url="http://www.NetBSD.org/developers/releng/index.html"></ulink>
   </para>
 
-  <para>[12] John Baldwin's FreeBSD Release Engineering Proposal
+  <para>[11] John Baldwin's FreeBSD Release Engineering Proposal
   <ulink url="http://people.FreeBSD.org/~jhb/docs/releng.txt"></ulink>
   </para>
 
-  <para>[13] PXE Jumpstart Guide
+  <para>[12] PXE Jumpstart Guide
   <ulink
   url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/pxe/index.html"></ulink>
   </para>
 
-  <para>[14] Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic:
+  <para>[13] Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic:
   <ulink url="http://docs.FreeBSD.org/44doc/papers/releng.html">
 <emphasis>The Release Engineering of 4.3BSD</emphasis></ulink>
   </para>