summaryrefslogtreecommitdiff
path: root/docs/USERDB_AND_DESKTOPS.md
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2021-06-30 21:26:47 +0900
committerYu Watanabe <watanabe.yu+github@gmail.com>2021-06-30 23:33:00 +0900
commit387f695526c5b6028230da2e9039bca59388fd62 (patch)
tree65945517b2f0b85f63e3407e4f8d1f93f4dbcf4a /docs/USERDB_AND_DESKTOPS.md
parent3d62af7d235552af5ea9ec0a812cc522f6516574 (diff)
downloadsystemd-387f695526c5b6028230da2e9039bca59388fd62.tar.gz
tree-wide: "a" -> "an"
Diffstat (limited to 'docs/USERDB_AND_DESKTOPS.md')
-rw-r--r--docs/USERDB_AND_DESKTOPS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/USERDB_AND_DESKTOPS.md b/docs/USERDB_AND_DESKTOPS.md
index a19f746a26..babaaaf3c7 100644
--- a/docs/USERDB_AND_DESKTOPS.md
+++ b/docs/USERDB_AND_DESKTOPS.md
@@ -56,7 +56,7 @@ and only switches back to the shell's UI after the user re-authenticated there.
Note that this change in behavior is a good idea in any case, and does not
create any dependencies on `systemd-homed` or systemd-specific APIs. It's
simply a change of behavior regarding use of existing APIs, not a suggested
-hook-up to a any new API.
+hook-up to any new APIs.
A display manager which supports this kind of out-of-context screen lock
operation needs to inform systemd-homed about this so that systemd-homed knows