bagder: curl-www/libcurl/hiper _schedule.html,1.10,1.11

Update of /cvsroot/curl/curl-www/libcurl/hiper
In directory labb:/tmp/cvs-serv29821

Modified Files:
	_schedule.html 
Log Message:
spelling is not my biggest skill


Index: _schedule.html
===================================================================
RCS file: /cvsroot/curl/curl-www/libcurl/hiper/_schedule.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- _schedule.html	6 Dec 2005 11:18:28 -0000	1.10
+++ _schedule.html	6 Dec 2005 11:19:04 -0000	1.11
@@ -34,11 +34,11 @@
 
  MARKDATE(Dec 6 2005) Ok, I think I'll change my measuring approach and I will
  instead write up my own HTTP server and control that to allow it to either
- site perfectly quite (just keeping the connection alive) or to send an
- endless stream of data. By allowing the selection of behaviour be based on
- the URL, I should be able to modify my test program to run and test a given
- number of "active" connections with a given number of "existing connections".
- I guess the real-world URLs are too hard to use to make adequate tests with.
+ sit perfectly quiet (just keeping the connection alive) or to send an endless
+ stream of data. By allowing the selection of behaviour be based on the URL, I
+ should be able to modify my test program to run and test a given number of
+ "active" connections with a given number of "existing connections".  I guess
+ the real-world URLs are too hard to use to make adequate tests with.
 <p>
  I found this little benchmark on select() performace compared to other event
  systems: