From 5a117bf41bd4ad881325230fdb6a904eb04c76ec Mon Sep 17 00:00:00 2001
From: liuliuliu0221 <13478454399@163.com>
Date: Fri, 4 Sep 2026 22:02:02 +0800
Subject: [PATCH 1/2] docs: fix typos and grammar errors in README
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- "systemd-home" → "systemd-homed" (consistent with rest of document)
- "to get the working" → "to get this working"
- "retain access their" → "retain access to their"
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index c6512b37..550365b9 100644
--- a/README.md
+++ b/README.md
@@ -91,7 +91,7 @@ Before using `fscrypt`, you should consider other solutions:
   ["V1" Linux kernel encryption API](https://www.kernel.org/doc/html/v6.8/filesystems/fscrypt.html#limitations-of-v1-policies),
   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
+  migrating `systemd-homed` to the "V2" API is tracked
   [in this `systemd` issue](https://github.com/systemd/systemd/issues/18280).
   Issues with `systemd-homed` should be reported to the systemd developers.
 
@@ -558,7 +558,7 @@ The `fscrypt` PAM module implements the Auth, Session, and Password
 
 The Password functionality of `pam_fscrypt.so` is used to automatically rewrap
 a user's login protector when their unix passphrase changes. An easy way to get
-the working is to add the line:
+this working is to add the line:
 ```
 password    optional    pam_fscrypt.so
 ```
@@ -1064,7 +1064,7 @@ guidelines in `CONTRIBUTING.md`. We will try our best to help.
 
 Usually, the PAM module `pam_fscrypt.so` will automatically detect changes to a
 user's login passphrase and update the user's `fscrypt` login protector so that
-they retain access their login-passphrase protected directories.  However,
+they retain access to their login-passphrase protected directories.  However,
 sometimes a user's login passphrase can become desynchronized from their
 `fscrypt` login protector.  This can happen if `root` assigns the user a new
 passphrase without providing the old one, if the user's login passphrase is

From a3f9e79bf7dd794410c06908b705ff3ab853bf78 Mon Sep 17 00:00:00 2001
From: liuliuliu0221 <13478454399@163.com>
Date: Fri, 4 Sep 2026 22:02:02 +0800
Subject: [PATCH 2/2] chore: trigger CLA re-check