man: Two finalization fixes

From PR review.

diff --git a/man/ostree-admin-deploy.xml b/man/ostree-admin-deploy.xml
index 30b5e90ac36fd7a2b04696ae0d47e856d7c10571..5ad71cafcae88015c5f604d38f0d14b8d14f8c18 100644 (file)
--- 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 0dc31e8b8c2e41c3ded676a9d71f444c561c746e..ac469b7ca15dc7dc947c0b890e4bb089b275336e 100644 (file)
--- 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