From 207df45fb4a8bf07cc6b049693164671b223d743 Mon Sep 17 00:00:00 2001
From: gumball76 <246793920+gumball76@users.noreply.github.com>
Date: Sat, 29 Nov 2025 13:56:43 -0600
Subject: [PATCH] README: fix Home Manager Systemd unit configuration

Since Home Manager relies on the naming scheme used by Systemd, the
current way to set a dependent service defined in the README fails as
Systemd doesn't support it.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 908f3f8..328be60 100644
--- a/README.md
+++ b/README.md
@@ -851,7 +851,7 @@ The actual sops configuration is in the `sops` namespace in your home.nix (or in
 The secrets are decrypted in a systemd user service called `sops-nix`, so other services needing secrets must order after it:
 ```nix
 {
-  systemd.user.services.mbsync.unitConfig.After = [ "sops-nix.service" ];
+  systemd.user.services.mbsync.Unit.After = [ "sops-nix.service" ];
 }
 ```