| Subject: | Spelling Mistakes |
Hi:
I discovered some spelling mistakes in the POD for this package. We've patched it for the Debian package; you may want to apply these changes in your version control. Note we neither need nor are we asking for another release, as I think that would put undue burden on the CPAN mirrors for such a tiny issue.
--- a/lib/POE/Queue.pm
+++ b/lib/POE/Queue.pm
@@ -60,7 +60,7 @@
=head1 DESCRIPTION
Priority queues may be implemented a number of ways, but they tend to
-behave similiar to lists that are kept in order by some kind of
+behave similar to lists that are kept in order by some kind of
"priority". Enqueued items are stored such that the "next" item to be
retrieved is the one with the highest priority. Subsequent fetches
return the next lowest priority, and so on, until the queue is
@@ -135,7 +135,7 @@
=head2 get_next_priority
-Returns the priority of the item at the nead of the queue. This is
+Returns the priority of the item at the head of the queue. This is
the lowest numeric priority in the queue.
get_next_priority() can be useful for checking the queue to see if
--- a/lib/POE/Wheel/ReadWrite.pm
+++ b/lib/POE/Wheel/ReadWrite.pm
@@ -941,7 +941,7 @@
wheel's Filter and buffered and written by its Driver.
put() returns true if a HighMark has been set and the Driver's output
-buffer has reached or exceded the limit. False is returned if
+buffer has reached or exceeded the limit. False is returned if
HighMark has not been set, or if the Driver's buffer is smaller than
that limit.