Index: general.ent
===================================================================
--- general.ent	(revision b3aacc06cbffda76e8415abbeeb04bf858b64a9b)
+++ general.ent	(revision 63d51c9aba9dc4ab9f6fa2137ef8ccd7655fa51d)
@@ -4,5 +4,5 @@
 -->
 
-<!ENTITY day          "19">                   <!-- Always 2 digits -->
+<!ENTITY day          "27">                   <!-- Always 2 digits -->
 <!ENTITY month        "12">                   <!-- Always 2 digits -->
 <!ENTITY year         "2012">
@@ -10,5 +10,5 @@
 <!ENTITY copyholder   "The BLFS Development Team">
 <!ENTITY version      "&year;-&month;-&day;">
-<!ENTITY releasedate  "December 19th, &year;">
+<!ENTITY releasedate  "December 27th, &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision b3aacc06cbffda76e8415abbeeb04bf858b64a9b)
+++ introduction/welcome/changelog.xml	(revision 63d51c9aba9dc4ab9f6fa2137ef8ccd7655fa51d)
@@ -44,4 +44,15 @@
 
 -->
+    <listitem>
+      <para>December 27th, 2012</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Corrected the example bridge configuration
+          file to use INTERFACE_COMPONENTS in accordance with the LFS 
+          network scripts.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>December 19th, 2012</para>
Index: networking/netprogs/bridgeutils.xml
===================================================================
--- networking/netprogs/bridgeutils.xml	(revision b3aacc06cbffda76e8415abbeeb04bf858b64a9b)
+++ networking/netprogs/bridgeutils.xml	(revision 63d51c9aba9dc4ab9f6fa2137ef8ccd7655fa51d)
@@ -131,9 +131,9 @@
       bootscripts dated January 27, 2012 or later.</para></note>
 
-      <para>The following configuration file will create a bridge device
-      at boot time and attach the eth0 device to it.  If more than one
-      device is desired, use a space separated list of INTERFACES.  This
-      configuration is useful when planning to run a virtual machine
-      such as kvm/qemu.</para>
+      <para>The following configuration file will create a bridge device at
+      boot time and attach the eth0 device to it.  If more than one device is
+      desired, use a space separated list of INTERFACE_COMPONENTS.  This
+      configuration is useful when planning to run a virtual machine such as
+      kvm/qemu.</para>
 
       <para>Other SERVICE combinations are possible, for example, 
@@ -143,10 +143,10 @@
       additional subsequent configuration.</para>
 
-      <caution><para>Do not run a parallel configuration for a device
-      in the INTERFACES list.  For instance, in the example below,
-      do not configure <filename>/etc/sysconfig/ifconfig.eth0</filename>
-      to run at boot time.  The command <command>ifdown br0</command>
-      followed by  command <command>ifup eth0</command> will work, but
-      don't try to have both up at the same time.</para></caution>
+      <caution><para>Do not run a parallel configuration for a device in the
+      INTERFACE_COMPONENTS list.  For instance, in the example below, do not
+      configure <filename>/etc/sysconfig/ifconfig.eth0</filename> to run at
+      boot time.  The command <command>ifdown br0</command> followed by
+      command <command>ifup eth0</command> will work, but don't try to have
+      both up at the same time.</para></caution>
       
 <screen role="root"><userinput>cat &gt; /etc/sysconfig/ifconfig.br0 &lt;&lt; "EOF"
@@ -160,5 +160,5 @@
 CHECK_LINK=no                 # Don't check before bridge is created
 STP=no                        # Spanning tree protocol, default no
-INTERFACES="eth0"             # Add to IFACE, space separated devices 
+INTERFACE_COMPONENTS="eth0"   # Add to IFACE, space separated devices 
 IP_FORWARD=true</literal>
 EOF</userinput></screen>
