fixed spelling in documentation (feedback from Debian)

Author: noxxi

lib/Net/SIP/Dispatcher/Eventloop.pod

@@ -60,7 +60,7 @@ existing event loop.
 If B<RW> is 0 (EV_READ) no more checking for readability of B<HANDLE> will be
 done. If B<RW> is 1 (EV_WRITE) no more checking for writeability of B<HANDLE>
 will be done.
-If B<RW> is not given it will remove B<HANDLE> from the loop completly, i.e.
+If B<RW> is not given it will remove B<HANDLE> from the loop completely, i.e.
 for both read and write.
 
 =item add_timer( WHEN, CALLBACK, [ REPEAT ] )

lib/Net/SIP/Leg.pod

@@ -147,7 +147,7 @@ B<get_legs> in L<Net::SIP::Dispatcher> to get all legs matching specific
 criteria. The B<SPEC> can contain the keys C<addr>, C<port> and C<proto>
 which match the arguments given during construction of the leg or are obtained
 from the legs socket.
-Additionally C<sub> can be used to specifiy a function which gets called with
+Additionally C<sub> can be used to specify a function which gets called with
 the leg object and must return true on match only.
 
 The method returns true if there was a full match and false otherwise.

lib/Net/SIP/SocketPool.pod

@@ -36,7 +36,7 @@ specific party, like an outgoing SIP proxy.
 In the common case that B<CONNECTED> is false the optional B<DST>
 given as C<< [ip, port, family] >> will be interpreted as restriction for the
 communication, i.e. it will be forced as destination in B<sendto> no matter what
-was given and it will be checked that any received data orgin from the expected
+was given and it will be checked that any received data origin from the expected
 peer B<DST>.
 
 =back