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
39
40
|
Description: spelling fix
Origin: vendor
Bug: https://rt.cpan.org/Ticket/Display.html?id=88034
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=88034
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2019-07-19
--- a/lib/KiokuDB/Backend/Role/UnicodeSafe.pm
+++ b/lib/KiokuDB/Backend/Role/UnicodeSafe.pm
@@ -41,7 +41,7 @@
store unicode perl strings safely.
This means that B<character> strings inserted to the database will not be
-retreived as B<byte> strings upon deserialization.
+retrieved as B<byte> strings upon deserialization.
This mostly has to do with L<KiokuDB::Backend::Serialize> variants.
--- a/lib/KiokuDB.pm
+++ b/lib/KiokuDB.pm
@@ -842,7 +842,7 @@
L<Directory::Transactional> may provide alternative mechanisms in the future.
Concurrency support in L<KiokuDB::Backend::DBI> depends on the database. SQLite
-defaults to serializable transaction isolation out of the box, wheras MySQL and
+defaults to serializable transaction isolation out of the box, whereas MySQL and
PostgreSQL default to read committed.
Depending on your application read committed isolation may be sufficient, but
--- a/lib/KiokuDB/Backend/Serialize/YAML.pm
+++ b/lib/KiokuDB/Backend/Serialize/YAML.pm
@@ -118,7 +118,7 @@
=item deserialize_from_stream $fh
-Reads until a YAML document boundry is reached, and then deserializes the
+Reads until a YAML document boundary is reached, and then deserializes the
current buffer.
=back
|
