summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2007-11-12 18:40:21 +0000
committerroot <root>2007-11-12 18:40:21 +0000
commita97e74e3908d62230e834fd7b30f2869136eef31 (patch)
tree08549e185b8e7f893ec9b3e6ddb88f41e0cea53a
parenta04347e5cbe92a5f99231dcdb3d7d0f474bad401 (diff)
*** empty log message ***
-rw-r--r--ev.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/ev.pod b/ev.pod
index c162b21..a3bcef3 100644
--- a/ev.pod
+++ b/ev.pod
@@ -419,7 +419,7 @@ level-triggering because you keep receiving events as long as the
condition persists. Remember you can stop the watcher if you don't want to
act on the event and neither want to receive future events).
-In general you can register as many read and/or write event watchers oer
+In general you can register as many read and/or write event watchers per
fd as you want (as long as you don't confuse yourself). Setting all file
descriptors to non-blocking mode is also usually a good idea (but not
required if you know what you are doing).