Skip Menu |
 

This queue is for tickets about the POE-Component-IRC CPAN distribution.

Report information
The Basics
Id: 53277
Status: resolved
Priority: 0/
Queue: POE-Component-IRC

People
Owner: Nobody in particular
Requestors: JAWNSY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 6.18
Fixed in: (no value)



Subject: Spelling Mistakes
Hi:

I discovered two 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/Component/IRC.pm
+++ b/lib/POE/Component/IRC.pm
@@ -1896,7 +1896,7 @@
 
 SSL support requires L<POE::Component::SSLify|POE::Component::SSLify>, as well
 as an IRC server that supports SSL connections. If you're missing
-POE::Component::SSLify, specifing B<'UseSSL'> will do nothing. The default is to
+POE::Component::SSLify, specifying B<'UseSSL'> will do nothing. The default is to
 not try to use SSL.
 
 Setting B<'Raw'> to true, will enable the component to send
@@ -2688,7 +2688,7 @@
 
 =head3 C<irc_delay_set>
 
-Emitted on a succesful addition of a delayed event using the
+Emitted on a successful addition of a delayed event using the
 L<C<delay>|/"delay"> method. C<ARG0> will be the alarm_id which can be used
 later with L<C<delay_remove>|/"delay_remove">. Subsequent parameters are
 the arguments that were passed to L<C<delay>|/"delay">.
@@ -2821,7 +2821,7 @@
 8-bits, and in ASCII. This has resulted in most of the Western world settling
 on ASCII-compatible Latin-1 as a convention. Recently, popular clients have
 begun sending a mixture of Latin-1 and UTF-8 over the wire to allow more
-characters without breaking backward compatability (too much). To decode such
+characters without breaking backward compatibility (too much). To decode such
 messages reliably, see
 L<C<irc_to_utf8>|POE::Component::IRC::Common/"irc_to_utf8"> in
 L<POE::Component::IRC::Common|POE::Component::IRC::Common>.
--- a/lib/POE/Component/IRC/Common.pm
+++ b/lib/POE/Component/IRC/Common.pm
@@ -557,7 +557,7 @@
 
 =head2 C<strip_color>
 
-Takes one paramter, a string of IRC text. Returns the string stripped of all
+Takes one parameter, a string of IRC text. Returns the string stripped of all
 IRC color codes. Due to the fact that both color and formatting codes can
 be cancelled with the same character, this might strip more than you hoped for
 if the string contains both color and formatting codes. Stripping both will
@@ -565,7 +565,7 @@
 
 =head2 C<strip_formatting>
 
-Takes one paramter, a string of IRC text. Returns the string stripped of all
+Takes one parameter, a string of IRC text. Returns the string stripped of all
 IRC formatting codes. Due to the fact that both color and formatting codes can
 be cancelled with the same character, this might strip more than you hoped for
 if the string contains both color and formatting codes. Stripping both will
--- a/lib/POE/Component/IRC/Projects.pod
+++ b/lib/POE/Component/IRC/Projects.pod
@@ -98,7 +98,7 @@
 constructor it will connect to a channel on a server and immediately send
 everyone on that channel a message privately. It will also send the same
 message to the channel itself publically at the specified interval. All users
-joining the channel thereafter will also recieve the message.
+joining the channel thereafter will also receive the message.
 
 =back
 
--- a/lib/POE/Component/IRC/State.pm
+++ b/lib/POE/Component/IRC/State.pm
@@ -1399,7 +1399,7 @@
 See also L<C<irc_nick>|POE::Component::IRC/"irc_nick"> in
 L<POE::Component::IRC|POE::Component::IRC>.
 
-Additional paramter C<ARG2> contains an arrayref of channel names that are
+Additional parameter C<ARG2> contains an arrayref of channel names that are
 common to the nick hanging client and the component.
 
 =head3 C<irc_kick>
Thanks, I have applied the patch.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.