diff options
author | sf-exg <sf-exg> | 2011-01-11 08:43:48 +0000 |
---|---|---|
committer | sf-exg <sf-exg> | 2011-01-11 08:43:48 +0000 |
commit | aadd8d3f7dd603cf8f4d2d0213bb3dbc0c3b3d53 (patch) | |
tree | 611ab41c22e10edd780d2258cef1482851b15379 | |
parent | 4734cf4db2f0ef5bf97287e2d8223ea8d8e430a0 (diff) |
Fix typo.
-rw-r--r-- | ev.pod | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1620,8 +1620,8 @@ write) will still block on the disk I/O. Another way to view it is that in the case of sockets, pipes, character devices and so on, there is another party (the sender) that delivers data -on it's own, but in the case of files, there is no such thing: the disk -will not send data on it's own, simply because it doesn't know what you +on its own, but in the case of files, there is no such thing: the disk +will not send data on its own, simply because it doesn't know what you wish to read - you would first have to request some data. Since files are typically not-so-well supported by advanced notification |