diff options
| author | Frantisek Sumsal <frantisek@sumsal.cz> | 2020-05-01 18:51:33 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2020-05-03 10:23:25 +0200 |
| commit | 2d4f8cf467b6825c91276808250823a29ab461fe (patch) | |
| tree | d724181dde4aeeb456d9323d9e6fd672996d4bee | |
| parent | 2e4086060b42330c8b6b430227586dbb2d1eddb0 (diff) | |
| download | systemd-2d4f8cf467b6825c91276808250823a29ab461fe.tar.gz | |
man: fix few spelling errors
Reported by Fossies.org.
| -rw-r--r-- | man/sd_bus_message_open_container.xml | 2 | ||||
| -rw-r--r-- | man/sd_notify.xml | 2 | ||||
| -rw-r--r-- | src/core/main.c | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/man/sd_bus_message_open_container.xml b/man/sd_bus_message_open_container.xml index 5f6e7c10e8..5a65518719 100644 --- a/man/sd_bus_message_open_container.xml +++ b/man/sd_bus_message_open_container.xml @@ -63,7 +63,7 @@ <citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry> and similar functions. Containers behave like a stack. To nest containers inside each other, call <function>sd_bus_message_open_container()</function> multiple times without calling - <function>sd_bus_message_close_container()</function> inbetween. Each container will be nested inside the + <function>sd_bus_message_close_container()</function> in between. Each container will be nested inside the previous container. <parameter>type</parameter> represents the container type and should be one of <literal>r</literal>, <literal>a</literal>, <literal>v</literal> or <literal>e</literal> as described in <citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>. diff --git a/man/sd_notify.xml b/man/sd_notify.xml index 3e49386236..87b12c4bdf 100644 --- a/man/sd_notify.xml +++ b/man/sd_notify.xml @@ -272,7 +272,7 @@ <term>BARRIER=1</term> <listitem><para>Tells the service manager that the client is explicitly requesting synchronization by means of - closing the file descriptor sent with this command. The service manager gurantees that the processing of a <varname> + closing the file descriptor sent with this command. The service manager guarantees that the processing of a <varname> BARRIER=1</varname> command will only happen after all previous notification messages sent before this command have been processed. Hence, this command accompanied with a single file descriptor can be used to synchronize against reception of all previous status messages. Note that this command cannot be mixed with other notifications, diff --git a/src/core/main.c b/src/core/main.c index b5e2ef747a..49879d8e37 100644 --- a/src/core/main.c +++ b/src/core/main.c @@ -1220,7 +1220,7 @@ static int bump_rlimit_memlock(struct rlimit *saved_rlimit) { assert_cc(RLIM_INFINITY > 0); mm = physical_memory() / 8; /* Let's scale how much we allow to be locked by the amount of physical - * RAM. We allow an eigth to be locked by us, just to pick a value. */ + * RAM. We allow an eighth to be locked by us, just to pick a value. */ new_rlimit = (struct rlimit) { .rlim_cur = MAX3(HIGH_RLIMIT_MEMLOCK, saved_rlimit->rlim_cur, mm), |