From 17f0af7cc8a5259f6839b53e06c4c961195161c2 Mon Sep 17 00:00:00 2001
From: Derick Rethans <derick@php.net>
Date: Mon, 3 Jan 2005 12:51:36 +0000
Subject: [PATCH] - Unbreak build

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@176367 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/http/functions/setcookie.xml | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/reference/http/functions/setcookie.xml b/reference/http/functions/setcookie.xml
index 98a1c04c9a..4b1f4ef394 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.35 $ -->
+<!-- $Revision: 1.36 $ -->
 <!-- splitted from ./en/functions/http.xml, last change in rev 1.2 -->
   <refentry id="function.setcookie">
    <refnamediv>
@@ -317,15 +317,16 @@ one : cookieone
       The following RFC's may also be useful:
       <ulink url="&url.rfc;2109">RFC 2109</ulink> and 
       <ulink url="&url.rfc;2965">RFC 2695</ulink>
-      <para>
-       You may notice the <parameter>expire</parameter> parameter takes on a
-       Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY
-       HH:MM:SS GMT</literal>, this is because PHP does this conversion
-       internally.
-      </para>
-      <para>
-       <parameter>expire</parameter> is compared to the client's time which can
-       differ from server's time.
+     </para>
+     <para>
+      You may notice the <parameter>expire</parameter> parameter takes on a
+      Unix timestamp, as opposed to the date format <literal>Wdy, DD-Mon-YYYY
+      HH:MM:SS GMT</literal>, this is because PHP does this conversion
+      internally.
+     </para>
+     <para>
+      <parameter>expire</parameter> is compared to the client's time which can
+      differ from server's time.
      </para>
     </note>
     <note>