From afb890d5fc3d523c731eccfd3e453bb413a04a30 Mon Sep 17 00:00:00 2001
From: vidir-semaphor <vidir.valberg@semaphor.dk>
Date: Tue, 6 Oct 2026 13:57:25 +0200
Subject: [PATCH] Fix apparent copy-past error in (un)lock-secureboot-policy
 entry

(cherry picked from commit 8e39ca4bfa6c77c8639bbeb89ec938e6e6683cec)
---
 man/systemd-pcrlock.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/systemd-pcrlock.xml b/man/systemd-pcrlock.xml
index 5825949d0e..24f9978eb6 100644
--- a/man/systemd-pcrlock.xml
+++ b/man/systemd-pcrlock.xml
@@ -272,7 +272,7 @@
         currently enforced. This looks at the SecureBoot, PK, KEK, db, dbx, dbt, dbr EFI variables and
         predicts their measurements to PCR 7 ("secure-boot-policy") on the next boot.</para>
 
-        <para>Use <command>unlock-firmware-config</command> before applying SecureBoot policy updates. If
+        <para>Use <command>unlock-secureboot-policy</command> before applying SecureBoot policy updates. If
         the <filename>systemd-pcrlock-secureboot-policy.service</filename> unit is enabled it will
         automatically generate a pcrlock file from the policy discovered.</para>