diff --git a/reference/http/functions/setcookie.xml b/reference/http/functions/setcookie.xml
index bc37f1ca2b..3d583109a5 100644
--- a/reference/http/functions/setcookie.xml
+++ b/reference/http/functions/setcookie.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <!-- splitted from ./en/functions/http.xml, last change in rev 1.2 -->
   <refentry id="function.setcookie">
    <refnamediv>
@@ -19,15 +19,15 @@
      </methodsynopsis>
     <para>
      <function>setcookie</function> defines a cookie to be sent along
-     with the rest of the header information.  Cookies must be sent
-     <emphasis>before</emphasis> any other headers are sent (this is a
-     restriction of cookies, not PHP). This requires you to place
-     calls to this function before any <literal>&lt;html></literal> or
-     <literal>&lt;head></literal> tags.  If headers exist prior to 
-     calling this function, <function>setcookie</function> will fail 
-     and return &false;.  If <function>setcookie</function> successfully 
-     runs, it will return &true;  This does not mean the user accepted 
-     the cookie or not.
+     with the rest of the HTTP headers. Like other headers, cookies
+     must be sent <emphasis>before</emphasis> any output from your
+     script (this is a protocol restriction). This requires that you
+     place calls to this function prior to any output, including
+     <literal>&lt;html></literal> and <literal>&lt;head></literal> tags
+     as well as any whitespace. If output exists prior to calling this
+     function, <function>setcookie</function> will fail and return &false;.
+     If <function>setcookie</function> successfully runs, it will return
+     &true;. This does not indicate whether the user accepted the cookie.
     </para>
     <para>
      All the arguments except the <parameter>name</parameter> argument