cvs: phpdoc /en/functions session.xml
| From: | Egon Schmid | Date: | Sat, 23 Jun 2001 23:56:23 +0000 |
| Subject: | cvs: phpdoc /en/functions session.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969335583@lists.php.net to get a copy of this message | ||
eschmid Sun Jun 24 01:56:23 2001 EDT
Modified files:
/phpdoc/en/functions session.xml
Log:
Corrected in CVS.
Index: phpdoc/en/functions/session.xml
diff -u phpdoc/en/functions/session.xml:1.38 phpdoc/en/functions/session.xml:1.39
--- phpdoc/en/functions/session.xml:1.38 Wed Jun 20 19:21:08 2001
+++ phpdoc/en/functions/session.xml Sun Jun 24 01:56:22 2001
@@ -956,7 +956,7 @@
<para>
Session data is usually stored after your script terminated
without the need to call <function>session_end</function>, but as
- session data is locked to prevend concurrent writes only one
+ session data is locked to prevent concurrent writes only one
script may operate on a session at any time. When using framesets
together with sessions you will experience the frames loading one
by one due to this locking. You can reduce the time needed to