From bf3d0afc76b59301a3f1ac2bd24fdd1fa5134e7e Mon Sep 17 00:00:00 2001 From: sf-exg Date: Thu, 14 Jul 2011 08:51:29 +0000 Subject: Fix typos. --- eio.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/eio.pod b/eio.pod index e14c32e..eaee6ba 100644 --- a/eio.pod +++ b/eio.pod @@ -709,7 +709,7 @@ normal C call. Left alone, a group request will instantly move to the pending state and will be finished at the next call of C. -There usefulness stems from the fact that, if a subrequest is added to a +The usefulness stems from the fact that, if a subrequest is added to a group I a call to C, via C, then the group will not finish until all the subrequests have finished. @@ -740,10 +740,10 @@ can return as "the load request". =item 2) open the file, maybe Next, open the file with C and add the request to the group -request and you are finished steting up the request. +request and you are finished setting up the request. If, for some reason, you cannot C (path is a null ptr?) you -cna set C<< grp->result >> to C<-1> to signal an error and let the gorup +can set C<< grp->result >> to C<-1> to signal an error and let the group request finish on its own. =item 3) open callback adds more requests @@ -755,7 +755,7 @@ C<-1> to signal an error. Otherwise, malloc some memory or so and issue a read request, adding the read request to the group. -=item 4) continue issuign requests till finished +=item 4) continue issuing requests till finished In the real callback, check for errors and possibly continue with C or any other eio request in the same way. -- cgit v1.2.3