aboutsummaryrefslogtreecommitdiff
path: root/devel/p5-POE-Exceptions/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'devel/p5-POE-Exceptions/pkg-descr')
-rw-r--r--devel/p5-POE-Exceptions/pkg-descr2
1 files changed, 1 insertions, 1 deletions
diff --git a/devel/p5-POE-Exceptions/pkg-descr b/devel/p5-POE-Exceptions/pkg-descr
index 889c1807a80f..866b3ed1f7ac 100644
--- a/devel/p5-POE-Exceptions/pkg-descr
+++ b/devel/p5-POE-Exceptions/pkg-descr
@@ -5,7 +5,7 @@ whenever the code decides to bail out by die'ing.) If the signal handler
returns 1 (as in the example above), POE will assume that the handler
dealt with the signal appropriately. If the signal handler returns 0,
POE will assume that the handler does not want to deal with the signal
-and POE will propgate the exception as if the handler never existed.
+and POE will propagate the exception as if the handler never existed.
Caveat: POE::Exceptions will die on its own in the case of a double
exception fault. If the DIE signal handler itself throws an exception,