summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2008-10-24 08:30:01 +0000
committerroot <root>2008-10-24 08:30:01 +0000
commit73bedbba35ee8f86a70ef309ca2056a8ef873fcf (patch)
tree0083618a3f7f6c405446086d106b0cc89efc773f
parentc682ad77651a7b568a062258c14947bbca83b06e (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 91bc096..5b33333 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1045,7 +1045,7 @@ always C<0>, which is supposed to not be too high and not be too low :).
Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is
fine, as long as you do not mind that the priority value you query might
-or might not have been adjusted to be within valid range.
+or might not have been clamped to the valid range.
=item ev_invoke (loop, ev_TYPE *watcher, int revents)