From: Charles McGarvey Date: Mon, 1 Aug 2022 02:28:30 +0000 (-0600) Subject: Fix more documentation typos X-Git-Tag: v0.905~3 X-Git-Url: https://git.brokenzipper.com/gitweb?a=commitdiff_plain;h=b01f40aad5c23676c1e3d5e80cdf75097e32ffba;p=chaz%2Fp5-File-KDBX Fix more documentation typos --- diff --git a/lib/File/KDBX.pm b/lib/File/KDBX.pm index 1fc0067..ee6522d 100644 --- 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 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 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 5c2a2ee..aeb8950 100644 --- 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 from L worked in Windows, but it probably doesn't. I spent a couple hours applying various quirks to L and L 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.