X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=lib%2FZOOM.pod;h=fd8abbf8d22728a1b6eb7d6ca11044f018a7b9a1;hb=1a18b079807428305b7376022236e901e4f576ca;hp=908bba5148e5a1c075b2f32a590966e195d5a6b8;hpb=7bf889db4a2c15b79d5ac332c09d304ace400111;p=ZOOM-Perl-moved-to-github.git

diff --git a/lib/ZOOM.pod b/lib/ZOOM.pod
index 908bba5..fd8abbf 100644
--- a/lib/ZOOM.pod
+++ b/lib/ZOOM.pod
@@ -1,4 +1,4 @@
-# $Id: ZOOM.pod,v 1.32 2006-04-11 16:38:38 mike Exp $
+# $Id: ZOOM.pod,v 1.33 2006-04-11 16:40:08 mike Exp $
 
 use strict;
 use warnings;
@@ -1377,12 +1377,12 @@ The approach is as follows:
 
 Create several connections to the various servers, each of them having
 the option C<async> set, and with whatever additional options are
-required - e.g. setting the piggyback retrieval record-count so that
-records will be returned in search responses.
+required - e.g. the piggyback retrieval record-count can be set so
+that records will be returned in search responses.
 
 =item Operations
 
-Send searches to the connections, request record retrieval, etc.
+Send searches to the connections, request records, etc.
 
 =item Event harvesting
 
@@ -1391,8 +1391,8 @@ received from the servers.  Each time this function returns, it
 indicates which of the connections has fired; this connection can then
 be interrogated with the C<last_event()> method to discover what event
 has occurred, and the return value - an element of the C<ZOOM::Event>
-enumeration can be used to determine what to do next.  For example,
-the C<ZEND> operation indicates that no further operations are
+enumeration - can be tested to determine what to do next.  For
+example, the C<ZEND> event indicates that no further operations are
 outstanding on the connection, so any fetched records can now be
 immediately obtained.