aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2024-12-27 16:08:52 -0800
committerEric Biggers <ebiggers@google.com>2024-12-27 16:08:52 -0800
commit7a17e3a0f1e9c0dfa7eae11816f55c820f689d4f (patch)
treef4a29e403afb02210b045e21131281d27ad085b2 /README.md
parent094d62bfc76262da865a305783e9bb809af7998d (diff)
README.md: fix a typo
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index ed31ea1..58fd870 100644
--- a/README.md
+++ b/README.md
@@ -88,7 +88,7 @@ Before using `fscrypt`, you should consider other solutions:
`systemd-homed` has better integration with systemd than `fscrypt` does.
However, `systemd-homed` (as of systemd v255) uses the
["V1" Linux kernel encryption API](https://www.kernel.org/doc/html/v6.8/filesystems/fscrypt.html#limitations-of-v1-policies),
- while `fscrypt` perfers the "V2" API. The older API causes
+ while `fscrypt` prefers the "V2" API. The older API causes
[known issues](#some-processes-cant-access-unlocked-encrypted-files), and
migrating `systemd-home` to the "V2" API is tracked
[in this `systemd` issue](https://github.com/systemd/systemd/issues/18280).