1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
Description: fix a spelling mistake
Origin: vendor
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2015-10-17
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=107840
Bug: https://rt.cpan.org/Ticket/Display.html?id=107840
--- a/lib/Event/RPC/Client.pm
+++ b/lib/Event/RPC/Client.pm
@@ -786,7 +786,7 @@
The Storable module is known to be insecure, so it should
be taken as the last option only. By default the Client
would do so. You can prevent that by setting this option
-explicitely to 0. It's enabled by default. Most likely
+explicitly to 0. It's enabled by default. Most likely
the connection will fail in that case, because the server
only will offer Storable if no other serialiser is available.
--- a/lib/Event/RPC/Server.pm
+++ b/lib/Event/RPC/Server.pm
@@ -201,7 +201,7 @@
}
#-- By default we probe all supported formats, but
- #-- not Storable. User has to activate this explicitely.
+ #-- not Storable. User has to activate this explicitly.
if ( not $insecure_msg_fmt_ok ) {
delete $probe_formats{STOR};
}
@@ -898,7 +898,7 @@
The Storable module is known to be insecure. But for
backward compatibility reasons Event::RPC::Server accepts
clients which can't offer anything but Storable. You can
-prevent that by setting this option explicitely to 0. It's
+prevent that by setting this option explicitly to 0. It's
enabled by default.
=back
|
