diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index e2d77c6dd..ec0ad96f3 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -82,6 +82,10 @@ first a summary, then a detailed log.</para>
 </itemizedlist>
 </listitem>
 
+<listitem><para>April 16, 2005 [matt]: Removed references to statically linking
+the pass 1 toolchain which should have gone as part of bug 1061 (Andrew Benton)
+</para></listitem>
+
 <listitem><para>April 13, 2005 [manuel]: Spelling fixes pointed by Archiac.
 Added tags to fix the PDF look in chapter 06.</para></listitem>
 
diff --git a/chapter01/how.xml b/chapter01/how.xml
index b2390fb48..2654ce7d3 100644
--- a/chapter01/how.xml
+++ b/chapter01/how.xml
@@ -37,22 +37,18 @@ to compile a compiler, you need a compiler.</para>
 <para><xref linkend="chapter-temporary-tools"/> also shows the user how
 to build a first pass of the toolchain, including Binutils and GCC
 (first pass basically means these two core packages will be
-re-installed a second time). The programs from these packages will be
-linked statically in order to be used independently of the host
-system. The next step is to build Glibc, the C library. Glibc will be
-compiled by the toolchain programs built in the first pass. Then, a
-second pass of the toolchain will be built. This time, the toolchain
-will be dynamically linked against the newly built Glibc. The
-remaining <xref linkend="chapter-temporary-tools"/> packages are built
-using this second pass toolchain. When this is done, the LFS
-installation process will no longer depend on the host distribution,
-with the exception of the running kernel.</para>
+re-installed a second time). The next step is to build Glibc, the C library.
+Glibc will be compiled by the toolchain programs built in the first pass. Then,
+a second pass of the toolchain will be built. This time, the toolchain will be
+dynamically linked against the newly built Glibc. The remaining
+<xref linkend="chapter-temporary-tools"/> packages are built using this second
+pass toolchain. When this is done, the LFS installation process will no longer
+depend on the host distribution, with the exception of the running kernel.
+</para>
 
 <para>While this may initially seem like a lot of work to get away
 from a host distribution, a full technical explanation is provided at
-the beginning of <xref linkend="chapter-temporary-tools"/>, 
-including notes on the differences between
-statically and dynamically-linked programs.</para>
+the beginning of <xref linkend="chapter-temporary-tools"/>.</para>
 
 <para>In <xref linkend="chapter-building-system"/>, the full LFS system is
 built. The chroot (change root) program is used to enter a virtual
diff --git a/general.ent b/general.ent
index 506bf08be..0ae944f33 100644
--- a/general.ent
+++ b/general.ent
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "TESTING-20050413">
-<!ENTITY releasedate "April 13, 2005">
+<!ENTITY version "TESTING-20050416">
+<!ENTITY releasedate "April 16, 2005">
 <!ENTITY milestone "6.1">
 
 <!ENTITY lfs-root "http://www.linuxfromscratch.org/">