Bug #83113 for Net-DBus: Spelling errors in pod

Hi, there are many spelling errors in pod. Some of them are reported in the joined file. Cheers

Description: Spelling errors Author: Xavier Guimard <x.guimard@free.fr> Bug: <url in upstream bugtracker> Forwarded: <no|not-needed|url proving that it has been forwarded> Last-Update: 2013-02-04 --- a/lib/Net/DBus/Exporter.pm +++ b/lib/Net/DBus/Exporter.pm @@ -532,7 +532,7 @@ =over 4 -=item No paramters, no return values +=item No parameters, no return values A method which simply prints "Hello World" each time its called @@ -578,7 +578,7 @@ =item Annotating methods with metdata -A method which is targetted for removal, and also does not +A method which is targeted for removal, and also does not return any value sub PlayMP3 { --- a/lib/Net/DBus/RemoteService.pm +++ b/lib/Net/DBus/RemoteService.pm @@ -125,7 +125,7 @@ Retrieves a handle to the remote object provided by the service with the name of C<$object_path>. If the optional C<$interface> parameter is provided, the object will immediately be cast to the designated -interface. NB, it is only neccessary to cast an object to a specific +interface. NB, it is only necessary to cast an object to a specific interface if there are multiple interfaces on the object providing methods with the same name, or the remote object does support introspection. The returned object will be an instance of L<Net::DBus::RemoteObject>. --- a/lib/Net/DBus/Service.pm +++ b/lib/Net/DBus/Service.pm @@ -63,7 +63,7 @@ Create a new service, attaching to the bus provided in the C<$bus> parameter, which should be an instance of the L<Net::DBus> object. The C<$name> parameter is the -qualified service name. It is not usually neccessary to +qualified service name. It is not usually necessary to use this constructor, since services can be created via the C<export_service> method on the L<Net::DBus> object. --- a/lib/Net/DBus/Callback.pm +++ b/lib/Net/DBus/Callback.pm @@ -48,7 +48,7 @@ about a callback to be invoked at a later date. It is used when registering to receive events from the L<Net::DBus::Reactor> class. NB use of this module in application code is no longer -neccessary and it remains purely for backwards compatability. +necessary and it remains purely for backwards compatibility. Instead you can simply pass a subroutine code reference in any place where a callback is desired. --- a/lib/Net/DBus/Reactor.pm +++ b/lib/Net/DBus/Reactor.pm @@ -125,7 +125,7 @@ Creates a new event loop ready for monitoring file handles, or generating timeouts. Except in very unsual circumstances (examples -of which I can't think up) it is not neccessary or desriable to +of which I can't think up) it is not necessary or desriable to explicitly create new reactor instances. Instead call the L<main> method to get a handle to the singleton instance. @@ -597,7 +597,7 @@ =item $reactor->toggle_timeout($id, $status[, $interval]); Updates the state of a previously registered timeout -specifed by the C<$id> parameter. The C<$status> +specified by the C<$id> parameter. The C<$status> parameter specifies whether the timeout is to be enabled or disabled, while the optional C<$interval> parameter can be used to change the period of the timeout. --- a/lib/Net/DBus/RemoteObject.pm +++ b/lib/Net/DBus/RemoteObject.pm @@ -71,7 +71,7 @@ data can be used to automatically resolve the correct interface to call cases where method names are unique. Rather than using this constructor directly, it is preferrable to use the C<get_object> method on L<Net::DBus::RemoteService>, since this caches handles -to remote objects, eliminating unneccessary introspection data lookups. +to remote objects, eliminating unnecessary introspection data lookups. =cut @@ -97,7 +97,7 @@ Casts the object to a specific interface, returning a new instance of the L<Net::DBus::RemoteObject> specialized to the desired interface. It is only -neccessary to cast objects to a specific interface, if two interfaces +necessary to cast objects to a specific interface, if two interfaces export methods or signals with the same name, or the remote object does not support introspection. --- a/lib/Net/DBus/Test/MockObject.pm +++ b/lib/Net/DBus/Test/MockObject.pm @@ -65,7 +65,7 @@ !!!!! WARNING !!! This object & its APIs should be considered very experimental at -this point in time, and no guarentees about future API compatability +this point in time, and no guarentees about future API compatibility are provided what-so-ever. Comments & suggestions on how to evolve this framework are, however, welcome & encouraged. --- a/lib/Net/DBus/Test/MockMessage.pm +++ b/lib/Net/DBus/Test/MockMessage.pm @@ -201,7 +201,7 @@ =item my $interface = $msg->get_interface -Retrieves the name of the interface targetted by this message, possibly +Retrieves the name of the interface targeted by this message, possibly an empty string if there is no applicable interface for this message. =cut --- a/lib/Net/DBus/Test/MockConnection.pm +++ b/lib/Net/DBus/Test/MockConnection.pm @@ -72,7 +72,7 @@ =item my $con = Net::DBus::Test::MockConnection->new() Create a new mock connection object instance. It is not usually -neccessary to create instances of this object directly, instead +necessary to create instances of this object directly, instead the C<test> method on the L<Net::DBus> object can be used to get a handle to a test bus. --- a/lib/Net/DBus/Binding/Value.pm +++ b/lib/Net/DBus/Binding/Value.pm @@ -53,7 +53,7 @@ =item my $value = Net::DBus::Binding::Value->new($type, $value); Creates a wrapper for the perl value C<$value> marking it as having -the dbus data type C<$type>. It is not neccessary to call this method +the dbus data type C<$type>. It is not necessary to call this method directly, instead the data typing methods in the L<Net::DBus> object should be used. --- a/lib/Net/DBus/Binding/Message.pm +++ b/lib/Net/DBus/Binding/Message.pm @@ -210,7 +210,7 @@ =item my $interface = $msg->get_interface -Retrieves the name of the interface targetted by this message, possibly +Retrieves the name of the interface targeted by this message, possibly an empty string if there is no applicable interface for this message. =cut --- a/lib/Net/DBus/Tutorial/ExportingObjects.pod +++ b/lib/Net/DBus/Tutorial/ExportingObjects.pod @@ -177,7 +177,7 @@ use base qw(Net::DBus); use Net::DBus::Exporter qw(com.berrange.music.player.manager) -Next up, it is neccessary to provide data types for the parameters and return +Next up, it is necessary to provide data types for the parameters and return values of the methods. The L<Net::DBus::Exporter> module provides a method C<dbus_method> for this purpose, which takes three parameter, the name of the method being exported, an array reference of parameter types, and an array @@ -251,7 +251,7 @@ This object implements the C<org.freedesktop.DBus.Exporter> interface which has a method C<ListObject>. This enables clients to determine a list of all objects exported within a service. While not functionally -neccessary for most applications, it is none-the-less a useful tool for +necessary for most applications, it is none-the-less a useful tool for developers debugging applications, or wondering what a service provides. =head1 CONNECTING TO THE BUS @@ -274,7 +274,7 @@ my $bus = Net::DBus->find; my $player = Music::Player->new($bus); -With the service attached to the bus, it is merely neccessary to run +With the service attached to the bus, it is merely necessary to run the main event processing loop to listen out for & handle incoming DBus messages. So the above code is modified to start a simple reactor: