diff --git a/reference/outcontrol/functions/flush.xml b/reference/outcontrol/functions/flush.xml
index 3372f84dfa..40940f413d 100644
--- a/reference/outcontrol/functions/flush.xml
+++ b/reference/outcontrol/functions/flush.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
 <!-- splitted from ./en/functions/outcontrol.xml, last change in rev 1.1 -->
   <refentry id="function.flush">
    <refnamediv>
@@ -17,36 +17,34 @@
      using (CGI, a web server, etc).  This effectively tries to push
      all the output so far to the user's browser.
     </simpara>
-    <note>
-     <para>
-      <function>flush</function> has no effect on the buffering
-      scheme of your webserver or the browser on the client
-      side. 
-     </para>
-     <para>
-      Several servers, especially on Win32, will still buffer
-      the output from your script until it terminates before
-      transmitting the results to the browser. 
-     </para>
-     <para>
-      Server modules for Apache like mod_gzip may do buffering of their own
-      that will cause <function>flush</function> to not result in data being
-      sent immediately to the client.
-     </para>
-     <para>
-      Even the browser may buffer its input before displaying it. 
-      Netscape, for example, buffers text until it receives an
-      end-of-line or the beginning of a tag, and it won't render
-      tables until the &lt;/table&gt; tag of the outermost table is
-      seen.
-     </para>
-     <para>
-      Some versions of Microsoft Internet Explorer will only start to display
-      the page after they have received 256 bytes of output, so you may need to
-      send extra whitespace before flushing to get those browsers to display the
-      page.
-     </para>
-    </note>
+    <para>
+     <function>flush</function> has no effect on the buffering
+     scheme of your webserver or the browser on the client
+     side. 
+    </para>
+    <para>
+     Several servers, especially on Win32, will still buffer
+     the output from your script until it terminates before
+     transmitting the results to the browser. 
+    </para>
+    <para>
+     Server modules for Apache like mod_gzip may do buffering of their own
+     that will cause <function>flush</function> to not result in data being
+     sent immediately to the client.
+    </para>
+    <para>
+     Even the browser may buffer its input before displaying it. 
+     Netscape, for example, buffers text until it receives an
+     end-of-line or the beginning of a tag, and it won't render
+     tables until the &lt;/table&gt; tag of the outermost table is
+     seen.
+    </para>
+    <para>
+     Some versions of Microsoft Internet Explorer will only start to display
+     the page after they have received 256 bytes of output, so you may need to
+     send extra whitespace before flushing to get those browsers to display the
+     page.
+    </para>
    </refsect1>
   </refentry>