diff options
| -rw-r--r-- | catalog/systemd.catalog.in | 2 | ||||
| -rw-r--r-- | man/sd_event_add_memory_pressure.xml | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/catalog/systemd.catalog.in b/catalog/systemd.catalog.in index 82d4820b80..d3d03dafe7 100644 --- a/catalog/systemd.catalog.in +++ b/catalog/systemd.catalog.in @@ -558,7 +558,7 @@ Support: %SUPPORT_URL% Memory of process @_PID@ (@_COMM@) has been trimmed. Either on user request or as result of a memory pressure event, memory of the -process has been trimmed, returning unneded allocation caches and other +process has been trimmed, returning unneeded allocation caches and other resources back to the OS kernel, making them available for other components of the OS. diff --git a/man/sd_event_add_memory_pressure.xml b/man/sd_event_add_memory_pressure.xml index 46cae0d16d..5baa411dfa 100644 --- a/man/sd_event_add_memory_pressure.xml +++ b/man/sd_event_add_memory_pressure.xml @@ -147,7 +147,7 @@ <literal>full</literal> as second parameter, the latter takes threshold and period times in microseconds as parameters. For details about these three parameters see the PSI documentation. Note that these two calls must be invoked immediately after allocating the event source, as they must be configured before - polling begins. Also note that these calls will fail if memory pressure paramterization has been passed + polling begins. Also note that these calls will fail if memory pressure parameterization has been passed in via the <varname>$MEMORY_PRESSURE_WATCH</varname>/<varname>$MEMORY_PRESSURE_WRITE</varname> environment variables (or in other words: configuration supplied by a service manager wins over internal settings).</para> @@ -221,7 +221,7 @@ <listitem><para>This is returned by <function>sd_event_source_set_memory_pressure_type()</function> and <function>sd_event_source_set_memory_pressure_period()</function> if invoked on event sources - at a time later than immediately after allocting them.</para></listitem> + at a time later than immediately after allocating them.</para></listitem> </varlistentry> <varlistentry> |