From 78905ffb821763db9db33f15bfe33398b87dab6b Mon Sep 17 00:00:00 2001
From: Colin Walters <walters@verbum.org>
Date: Mon, 27 Nov 2023 13:50:07 -0500
Subject: [PATCH] man: Two finalization fixes

From PR review.
---
 man/ostree-admin-deploy.xml            | 2 +-
 man/ostree-admin-lock-finalization.xml | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/man/ostree-admin-deploy.xml b/man/ostree-admin-deploy.xml
index 30b5e90ac3..5ad71cafca 100644
--- a/man/ostree-admin-deploy.xml
+++ b/man/ostree-admin-deploy.xml
@@ -126,7 +126,7 @@ License along with this library. If not, see <https://www.gnu.org/licenses/>.
 
                 <listitem><para>
                     The deployment will not be "finalized" by default on shutdown; to later
-                    queue it, use <literal>ostree admin unlock-finalization</literal>.
+                    queue it, use <literal>ostree admin lock-finalization --unlock</literal>.
                 </para></listitem>
             </varlistentry>
 
diff --git a/man/ostree-admin-lock-finalization.xml b/man/ostree-admin-lock-finalization.xml
index 0dc31e8b8c..ac469b7ca1 100644
--- a/man/ostree-admin-lock-finalization.xml
+++ b/man/ostree-admin-lock-finalization.xml
@@ -61,7 +61,8 @@ License along with this library. If not, see <https://www.gnu.org/licenses/>.
             will be set into a "finalization locked" state, which means it will not be queued for the next boot by default.
         </para>
         <para>
-            This is the same as the <literal>--lock-finalization</literal> argument for <literal>ostree admin deploy</literal>.
+            This is the same as the <literal>--lock-finalization</literal> argument for <literal>ostree admin deploy</literal>,
+            which is the recommended way to use this feature in a race-free way.
         </para>
         <para>
             However more commonly, one will use the <literal>--unlock</literal> argument for this command to later unlock