sp Tue Oct 28 10:24:04 2003 EDT
Modified files:
/phpdoc/en/features persistent-connections.xml
Log:
Overlooked small typo
Index: phpdoc/en/features/persistent-connections.xml
diff -u phpdoc/en/features/persistent-connections.xml:1.23
phpdoc/en/features/persistent-connections.xml:1.24
--- phpdoc/en/features/persistent-connections.xml:1.23 Tue Oct 28 10:20:18 2003
+++ phpdoc/en/features/persistent-connections.xml Tue Oct 28 10:24:04 2003
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.23 $ -->
+<!-- $Revision: 1.24 $ -->
<chapter id="features.persistent-connections">
<title>Persistent Database Connections</title>
@@ -45,13 +45,13 @@
multiprocess web server, which currently only includes Apache. A
multiprocess server typically has one process (the parent) which
coordinates a set of processes (its children) who actually do the
- work of serving up web pages. When each request comes in from a
+ work of serving up web pages. When a request comes in from a
client, it is handed off to one of the children that is not already
serving another client. This means that when the same client makes
a second request to the server, it may be served by a different
child process than the first time. When opening a persistent connection,
every following page requesting SQL services can reuse the same
- entsablished connection to the SQL server.
+ established connection to the SQL server.
</simpara>
<simpara>
The last method is to use PHP as a plug-in for a multithreaded web
