Fix more documentation typos

diff --git a/lib/File/KDBX.pm b/lib/File/KDBX.pm
index 1fc0067e5cf7790bbf3ea1dac61cc891b7c1adfe..ee6522d8d3f7bc3aa9c506d3a1acd33360d7c44a 100644 (file)
--- a/lib/File/KDBX.pm
+++ b/lib/File/KDBX.pm
@@ -647,7 +647,7 @@ sub groups {
     $kdbx->add_entry($entry, %options);
     $kdbx->add_entry(%entry_attributes, %options);
 
-Add a entry to a database. This is equivalent to identifying a parent group and calling
+Add an entry to a database. This is equivalent to identifying a parent group and calling
 L<File::KDBX::Group/add_entry> on the parent group, forwarding the arguments. Available options:
 
 =for :list
@@ -1406,7 +1406,7 @@ secure the database when dumped. The attributes that will be randomized are:
 * L</transform_seed>
 
 Randomizing these values has no effect on a loaded database. These are only used when a database is dumped.
-You normally do not need to call this method explicitly because the dumper does it explicitly by default.
+You normally do not need to call this method explicitly because the dumper does it for you by default.
 
 =cut
 

diff --git a/lib/File/KDBX/Key/YubiKey.pm b/lib/File/KDBX/Key/YubiKey.pm
index 5c2a2eeb3bad014b508943336147486bafe98c0a..aeb8950cf084617505d03cc234f8e741db818376 100644 (file)
--- a/lib/File/KDBX/Key/YubiKey.pm
+++ b/lib/File/KDBX/Key/YubiKey.pm
@@ -95,7 +95,7 @@ sub challenge {
     @keys = File::KDBX::Key::YubiKey->scan(%options);
 
 Find connected, configured YubiKeys that are capable of responding to a challenge. This can take several
-second.
+seconds.
 
 Options:
 
@@ -151,7 +151,7 @@ sub scan {
     $device = $key->device($device);
 
 Get or set the device number, which is the index number starting and incrementing from zero assigned
-to the YubiKey device. If there is only one detected YubiKey device, it's number is C<0>.
+to the YubiKey device. If there is only one detected YubiKey device, its number is C<0>.
 
 Defaults to C<0>.
 
@@ -454,7 +454,7 @@ override the default programs, these environment variables can be used.
 This doesn't work yet on Windows, probably. The hangup is pretty silly: IPC. Theoretically it would work if
 C<run_forked> from L<IPC::Cmd> worked in Windows, but it probably doesn't. I spent a couple hours applying
 various quirks to L<IPC::Open3> and L<IPC::Cmd> implementations but never quite got it to worked reliably
-without deadlocks. Maybe I'll revisit this later. Hit me up so I know if there's demand.
+without deadlocks. Maybe I'll revisit this later. Hit me up so I know if there's interest.
 
 It would also be possible to implement this as an XS module that incorporated ykcore, using libusb-1 which
 would probably make it more portable with Windows. Perhaps if I get around to it.