From b47013fd77c3058768906e110827b0c1ff8c540c Mon Sep 17 00:00:00 2001 From: Benjamin Franzke Date: Sat, 28 May 2022 14:42:17 +0200 Subject: [PATCH] man/nspawn: fix boot-option related wording --- man/systemd-nspawn.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 8a527269d3f..668d9075094 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -74,7 +74,7 @@ As a safety check systemd-nspawn will verify the existence of /usr/lib/os-release or /etc/os-release in the container tree before - starting the container (see + starting a container (see os-release5). It might be necessary to add this file to the container tree manually if the OS of the container is too old to contain this file out-of-the-box. @@ -84,8 +84,8 @@ template unit file systemd-nspawn@.service is provided to make this easy, taking the container name as instance identifier. Note that different default options apply when systemd-nspawn is invoked by the template unit file than interactively on the command line. Most importantly the template unit file - makes use of the which is not the default in case systemd-nspawn is - invoked from the interactive command line. Further differences with the defaults are documented along with the + makes use of the option which is not the default in case systemd-nspawn + is invoked from the interactive command line. Further differences with the defaults are documented along with the various supported options below. The machinectl1 tool may @@ -121,7 +121,7 @@ Options - If option is specified, the arguments + If option is specified, the arguments are used as arguments for the init program. Otherwise, COMMAND specifies the program to launch in the container, and the remaining arguments are used as