Version 0.905

[chaz/p5-File-KDBX] / lib / File / KDBX / Key / YubiKey.pm

diff --git a/lib/File/KDBX/Key/YubiKey.pm b/lib/File/KDBX/Key/YubiKey.pm
index 838b296ebbd4679bd9d708b1be91bef60a0a600b..515b23ca514fcf0c060bd34df24c8a3a2506e759 100644 (file)
--- a/lib/File/KDBX/Key/YubiKey.pm
+++ b/lib/File/KDBX/Key/YubiKey.pm
@@ -14,7 +14,7 @@ use namespace::clean;
 
 extends 'File::KDBX::Key::ChallengeResponse';
 
-our $VERSION = '0.904'; # VERSION
+our $VERSION = '0.905'; # VERSION
 
 # It can take some time for the USB device to be ready again, so we can retry a few times.
 our $RETRY_COUNT    = 5;
@@ -296,7 +296,7 @@ File::KDBX::Key::YubiKey - A Yubico challenge-response key
 
 =head1 VERSION
 
-version 0.904
+version 0.905
 
 =head1 SYNOPSIS
 
@@ -336,7 +336,7 @@ See L<https://keepassxc.org/docs/#faq-yubikey-howto> for more information.
     $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>.
 
@@ -412,7 +412,7 @@ Get or set the L<ykinfo(1)> program name or filepath. Defaults to C<$ENV{YKINFO}
     @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:
 
@@ -485,7 +485,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.