this unit during
installation. This is best
configured via
- <varname>WantedBy=multi-uer.target</varname>
+ <varname>WantedBy=multi-user.target</varname>
in the unit's
<literal>[Install]</literal>
section.</para>
after it. Note that networking
daemons that simply provide
functionality to other hosts
- generally don't need to pull
+ generally do not need to pull
this in.</para>
</listitem>
</varlistentry>
<varname>Wants=</varname> type
dependency. If the unit wants
to be pulled in by the first
- remote mount showing up it
+ remote mount showing up, it
should use
<filename>network-online.target</filename>
(see above).</para>
<filename>smartcard.target</filename>,
<filename>sound.target</filename>.</para>
- <para>In addition the following special unit is
+ <para>In addition, the following special unit is
understood only when systemd runs as service instance:</para>
<variablelist>
manager should start this
unit. If systemd receives
<constant>SIGTERM</constant> or <constant>SIGINT</constant> when running
- as user service daemon it will
+ as user service daemon, it will
start this unit.</para>
<para>Normally, this pulls in
<varlistentry>
<term><filename>system.slice</filename></term>
<listitem>
- <para>By default all services
+ <para>By default, all services
services started by
<command>systemd</command> are
found in this slice.</para>
<varlistentry>
<term><filename>user.slice</filename></term>
<listitem>
- <para>By default all user
+ <para>By default, all user
processes and services started
on behalf of the user,
including the per-user systemd
<varlistentry>
<term><filename>machine.slice</filename></term>
<listitem>
- <para>By defalt all virtual
+ <para>By defalt, all virtual
machines and containers
registered with
<command>systemd-machined</command>