diff --git a/docs/traffic_shaping.xml b/docs/traffic_shaping.xml
index 420063057..0d060277d 100644
--- a/docs/traffic_shaping.xml
+++ b/docs/traffic_shaping.xml
@@ -148,7 +148,7 @@
     linkend="tcclasses">below</link>.</para>
 
     <para>You can shape incoming traffic through use of an
-    <firstterm>Intermediate Frame Block</firstterm> (IFB) device. <link
+    <firstterm>Intermediate Functional Block</firstterm> (IFB) device. <link
     linkend="IFB">See below</link>. <emphasis role="bold">But beware: using an
     IFB can result in queues building up both at your ISPs router and at your
     own.</emphasis></para>
@@ -428,7 +428,7 @@
         <listitem>
           <para>REDIRECTED INTERFACES — Entries are appropriate in this column
           only if the device in the INTERFACE column names a <link
-          linkend="IFB">Intermediate Frame Block (IFB)</link>. It lists the
+          linkend="IFB">Intermediate Functional Block (IFB)</link>. It lists the
           physical interfaces that will have their input shaped using classes
           defined on the IFB. Neither the IFB nor any of the interfaces listed
           in this column may have an IN-BANDWIDTH specified. You may specify
@@ -1783,7 +1783,7 @@ eth1            4       94mbit          full            4           default #for
   </section>
 
   <section id="IFB">
-    <title>Intermediate Frame Block (IFB) Devices</title>
+    <title>Intermediate Functional Block (IFB) Devices</title>
 
     <para>The principles behind an IFB is fairly simple:</para>