gawkinet.ps version 1.1: some more documentation bugs, andclarification request

[Neil Zanella]

page 4: 'usually referred as' should be 'usually referred to as'

page 5: comma after 'FTP (File Transfer Protocol)'

page 5: 'at the location' would better be 'at that location'

page 5: 'you have to have', repetition: suggestion: 'you must have'

page 6: 'communications are synchronous', etc... In Stevens' UNP book
        he illustrates full-duplex TCP connections as involving an
        upstream and a downstream, which looks asynchronous to me.
        So how come does the manual state thet 'communications are
        synchronous'. Is this simply the way it works in gawk?

        Also, with the C sockets API, writes don't block. Blocking
        is not as much a property of the protocol, as much as it
        is a property of the API implementing the protocol, AFAIK.
        With the sockets API, write() will return even before the
        data at the other end has been received. read() on the
        other hand, blocks until the data has been received or
        a FIN segment is received in which case it returns 0.

Thanks,

Neil