commit 6e2cdade7ebb49ea8f80eff499cf14f8351caa34
parent c2bc5a99a084883b184f72be49738abc81b60e2f
Author: Sean Enck <sean@ttypty.com>
Date: Thu, 26 Jun 2025 12:40:47 -0400
typo in readme
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -13,7 +13,7 @@ keyring or command for password input over using a GPG key and uses a keepass da
While `lb` uses a `.kdbx` formatted file that can be opened by a variety of tools, it is highly opinionated on how to store data in the database. Any
`.kdbx` used with `lb` should be managed by `lb` with a fallback ability to use other tools to alter the/view the file otherwise. Mainly lockbox itself
is using a common format so that it doesn't lock a user into a custom file format or dealing with gpg, age, etc. files and instead COULD be recovered
-via other tooling if needed. `lb` does try to place nice with standard fields used within kdbx files, but it may disagree how to manage/store/update them.
+via other tooling if needed. `lb` does try to play nice with standard fields used within kdbx files, but it may disagree how to manage/store/update them.
## configuration
