diff --git a/man/busctl.xml b/man/busctl.xml
index 3fdef7bd4d..ab18a49d0a 100644
--- a/man/busctl.xml
+++ b/man/busctl.xml
@@ -171,7 +171,7 @@ along with systemd; If not, see .
When showing the list of endpoints, show
- only endpoints which haven't actually been activated yet,
+ only endpoints which have actually not been activated yet,
but may be started automatically if accessed.
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 626d820151..50027b44dd 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -380,7 +380,7 @@
terse output, only
showing the actual
message of each journal
- entry with no meta data,
+ entry with no metadata,
not even a timestamp.
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 95164322f7..a814ec1ec3 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -269,12 +269,12 @@
violated when systemd-journald is
started, the value will be raised to
percentage that is actually free. This
- means that if before there was enough
- free space and journal files were
+ means that if there was enough
+ free space before and journal files were
created, and subsequently something
else causes the file system to fill
up, journald will stop using more
- space, but it'll will not removing
+ space, but it will not be removing
existing files to go reduce footprint
either.
diff --git a/man/machine-info.xml b/man/machine-info.xml
index ddf8f8b3d0..7448e68fd4 100644
--- a/man/machine-info.xml
+++ b/man/machine-info.xml
@@ -55,7 +55,7 @@
DescriptionThe /etc/machine-info file
- contains machine meta data.
+ contains machine metadata.
The basic file format of
machine-info is a
@@ -68,7 +68,7 @@
execution engine./etc/machine-info contains
- meta data about the machine that is set by the user or
+ metadata about the machine that is set by the user or
administrator.Depending on the operating system other
@@ -84,7 +84,7 @@
Options
- The following machine meta data parameters may
+ The following machine metadata parameters may
be set using
/etc/machine-info:
diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml
index 66d40fca45..3022cdb6f5 100644
--- a/man/pam_systemd.xml
+++ b/man/pam_systemd.xml
@@ -227,7 +227,7 @@
The following environment variables are read by
the module and may be used by the PAM service to pass
- meta data to the module:
+ metadata to the module:
diff --git a/man/sd_bus_creds_get_pid.xml b/man/sd_bus_creds_get_pid.xml
index 740082e478..25978a2895 100644
--- a/man/sd_bus_creds_get_pid.xml
+++ b/man/sd_bus_creds_get_pid.xml
@@ -225,7 +225,7 @@ along with systemd; If not, see .
Description
- Those functions return information from an
+ These functions return information from an
sd_bus_creds object. It may be created with
sd_bus_creds_new_from_pid3,
in which case it will describe the specified process, or it may be
@@ -311,7 +311,7 @@ along with systemd; If not, see .
sd_bus_creds_has_effective_cap will
check whether the capability specified by
capability was set in the effective
- capabilities mask. A positive return value means that is were
+ capabilities mask. A positive return value means that is was
set, zero means that it was not set, and a negative return
value signifies an error. See
capabilities7
diff --git a/man/sd_bus_error.xml b/man/sd_bus_error.xml
index 642b0b96d0..671df441ea 100644
--- a/man/sd_bus_error.xml
+++ b/man/sd_bus_error.xml
@@ -231,10 +231,10 @@ along with systemd; If not, see .
Description
- sd_bus_error structure carries
+ The sd_bus_error structure carries
information for a sd-bus error.
Functions described below can be used to set and query fields in
- this structure. Field name contains a
+ this structure. The name field contains a
short identifier of an error. It should follow the rules for error
names described in the D-Bus specification, subsection Valid
@@ -251,16 +251,16 @@ along with systemd; If not, see .
and the remaining ones to -ENXIO. Well-known
D-Bus error names are available as constants
SD_BUS_ERROR_FAILED, etc., listed above. If
- name is NULL, it is is
+ name is NULL, it is
assumed that no error occured, and 0 is returned. This means that
this function may be conveniently used in a
return statement.If e is not
NULL, name and
- message will be filled-in in the
+ message in the
sd_bus_error structure
- e points at. As described above,
+ e points at will be filled in. As described above,
name may be NULL,
which is treated as no error. Parameter
message may also be
@@ -307,7 +307,7 @@ along with systemd; If not, see .
e. If the strings in
e were set using
sd_bus_set_error_const, they will be shared.
- Otherwie, they wil be copied.
+ Otherwise, they will be copied.sd_bus_error_is_set will return
true if e is
diff --git a/man/sd_bus_open_user.xml b/man/sd_bus_open_user.xml
index 0effee461d..22a4f616f0 100644
--- a/man/sd_bus_open_user.xml
+++ b/man/sd_bus_open_user.xml
@@ -100,7 +100,7 @@ along with systemd; If not, see .
sd_bus_open_system() does the same, but
connects to the system bus.
- If $DBUS_SESSION_BUS_ADDRESS environment
+ If the $DBUS_SESSION_BUS_ADDRESS environment
variable is set
(c.f. environ7),
it will be used as the address of the user bus. This variable can
@@ -108,7 +108,7 @@ along with systemd; If not, see .
this variable is not set, a suitable default for the default user
D-Bus instance will be used.
- If $DBUS_SYSTEM_BUS_ADDRESS environment
+ If the $DBUS_SYSTEM_BUS_ADDRESS environment
variable is set, it will be used as the address of the system
bus. This variable uses the same syntax as
$DBUS_SESSION_BUS_ADDRESS/. If this variable is
@@ -158,7 +158,7 @@ along with systemd; If not, see .
sd_bus_unref3.
- Functions sd_bus_default_user() and
+ The functions sd_bus_default_user() and
sd_bus_default_system() do not create a new
reference.
diff --git a/man/sd_journal_print.xml b/man/sd_journal_print.xml
index 7b08733171..638657721f 100644
--- a/man/sd_journal_print.xml
+++ b/man/sd_journal_print.xml
@@ -203,7 +203,7 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid(
be guaranteed. Using
sd_journal_print() has the
benefit of logging source code line, filenames, and
- functions as meta data along all entries, and
+ functions as metadata along all entries, and
guaranteeing chronological ordering with structured
log entries that are generated via
sd_journal_send(). Using
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 418e71f779..d6d2c76f2e 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -1444,7 +1444,7 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
[] may be used. See
glob7
for more details. The patterns are matched against the names of
- currently loaded units, and patterns which don't match anything
+ currently loaded units, and patterns which do not match anything
are silently skipped. For example:
# systemctl stop sshd@*.service
will stop all sshd@.service instances.
diff --git a/man/systemd-coredumpctl.xml b/man/systemd-coredumpctl.xml
index 286ff14639..4318a2fd44 100644
--- a/man/systemd-coredumpctl.xml
+++ b/man/systemd-coredumpctl.xml
@@ -135,7 +135,7 @@
Extract the last coredump
matching specified characteristics.
- Coredump will be written on standard output,
+ The coredump will be written on standard output,
unless an output file is specified with
.
diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index 0a20e21159..4d2cb40805 100644
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -66,10 +66,10 @@
syslog3
call, from standard input and standard error of system
services or via its native API. It will implicitly
- collect numerous meta data fields for each log
+ collect numerous metadata fields for each log
messages in a secure and unfakeable way. See
systemd.journal-fields7
- for more information about the collected meta data.
+ for more information about the collected metadata.
Log data collected by the journal is primarily
diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index 5bddd89503..b34d38c9b5 100644
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -179,8 +179,8 @@
Turns off any status
output by the tool itself. When this
- switch is used, then the only output
- by nspawn will be the console output
+ switch is used, the only output
+ from nspawn will be the console output
of the container OS itself.
@@ -303,14 +303,14 @@
Create a virtual
- ethernet link between host and
+ Ethernet link between host and
container. The host side of the
- ethernet link will be available as
+ Ethernet link will be available as a
network interface named after the
container's name (as specified with
), prefixed
with ve-. The
- container side of the the ethernet
+ container side of the the Ethernet
link will be named
host0. Note that
@@ -322,7 +322,7 @@
Adds the host side of the
- ethernet link created with
+ Ethernet link created with
to the specified bridge. Note that
@@ -540,13 +540,13 @@
container in, simply register the
service or scope unit
systemd-nspawn has
- been invoked in in
+ been invoked in with
systemd-machined8. This
has no effect if
is
used. This switch should be used if
systemd-nspawn is
- invoked from within an a service unit,
+ invoked from within a service unit,
and the service unit's sole purpose
is to run a single
systemd-nspawn
diff --git a/man/systemd-system.conf.xml b/man/systemd-system.conf.xml
index 6c1b1e7ee7..f3a89ad459 100644
--- a/man/systemd-system.conf.xml
+++ b/man/systemd-system.conf.xml
@@ -99,7 +99,7 @@
Configures the initial
CPU affinity for the init
process. Takes a space-separated list
- of CPU indexes.
+ of CPU indices.
@@ -216,7 +216,7 @@
Takes a
space-separated list of architecture
- identifiers. Selects of which
+ identifiers. Selects from which
architectures system calls may be
invoked on this system. This may be
used as an effective way to disable
diff --git a/man/systemd-udevd.service.xml b/man/systemd-udevd.service.xml
index 0e49fa07f6..bb04694342 100644
--- a/man/systemd-udevd.service.xml
+++ b/man/systemd-udevd.service.xml
@@ -83,7 +83,7 @@
Delay the execution of RUN
- instruction by the given number of seconds. This option
+ instructions by the given number of seconds. This option
might be useful when debugging system crashes during
coldplug caused by loading non-working kernel
modules.
@@ -148,7 +148,7 @@
udev.exec-delay=rd.udev.exec-delay=
- Delay the execution of RUN instruction by the given
+ Delay the execution of RUN instructions by the given
number of seconds. This option might be useful when
debugging system crashes during coldplug caused by loading
non-working kernel modules.
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index c08feba27e..252992bc60 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -248,7 +248,7 @@
Controls the CPU
affinity of the executed
processes. Takes a space-separated
- list of CPU indexes. This option may
+ list of CPU indices. This option may
be specified more than once in which
case the specificed CPU affinity masks
are merged. If the empty string is
@@ -1041,14 +1041,14 @@
add or delete the listed system calls
from the set of the filtered system
calls, depending of its type and the
- default action (e.g. You have started
+ default action. (For example, if you have started
with a whitelisting of
read and
write, and right
after it add a blacklisting of
write, then
write will be
- removed from the set).
+ removed from the set.)
Note that setting
diff --git a/man/systemd.journal-fields.xml b/man/systemd.journal-fields.xml
index c93b5da1dc..d77e6eb1b6 100644
--- a/man/systemd.journal-fields.xml
+++ b/man/systemd.journal-fields.xml
@@ -529,7 +529,7 @@
JSON Format, the addresses of journal entries
are serialized into fields prefixed with double
underscores. Note that these are not proper fields when
- stored in the journal but for addressing meta data of
+ stored in the journal but for addressing metadata of
entries. They cannot be written as part of structured
log entries via calls such as
sd_journal_send3. They
diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml
index f495fe3666..5e9b39f38f 100644
--- a/man/systemd.socket.xml
+++ b/man/systemd.socket.xml
@@ -90,9 +90,9 @@
systemd.service5
for more information about .service files). The name
of the .service unit is by default the same as the
- name of the .socket unit, but can be altered with
+ name of the .socket unit, but can be altered with the
option described below.
- Depending on the setting of
+ Depending on the setting of the
option described below, this .service unit must either
be named like the .socket unit, but with the suffix
replaced, unless overridden with
@@ -135,7 +135,7 @@
Socket units may be used to implement on-demand
starting of services, as well as parallelized starting
of services. See the blog stories linked at the end
- for introduction.
+ for an introduction.Note that the daemon software configured for
socket activation with socket units needs to be able
diff --git a/man/udev.xml b/man/udev.xml
index 1bf0b089e2..da4ff220b9 100644
--- a/man/udev.xml
+++ b/man/udev.xml
@@ -874,7 +874,7 @@
An ordered, space-separated list of policies by which the
interface name should be set. NamePolicy may
- be disabeld by specifying net.ifnames=0 on the
+ be disabeled by specifying net.ifnames=0 on the
kernel commandline. Each of the policies may fail, and the first
successfull one is used. The name is not set directly, but
is exported to udev as the property ID_NET_NAME,