diff options
author | Colin Watson <cjwatson@debian.org> | 2024-05-08 16:01:01 +0200 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-05-08 17:14:32 +0200 |
commit | 566491c971730ea262e3df081cd91d67a3ab104c (patch) | |
tree | 818dbdd1c93a5f82650a4fb9b183fa7e10541614 /man/sd_bus_set_address.xml | |
parent | pidfd: properly detect if libc offers pidfd syscalls and make use of them then (diff) | |
download | systemd-566491c971730ea262e3df081cd91d67a3ab104c.tar.xz systemd-566491c971730ea262e3df081cd91d67a3ab104c.zip |
docs,man: Avoid some ambiguous uses of "may not"
Like much English text, the systemd documentation uses "may not" in the
sense of both "will possibly not" and "is forbidden to". In many cases
this is OK because the context makes it clear, but in others I felt it
was possible to read the "is forbidden to" sense by mistake: in
particular, I tripped over "the target file may not exist" in
systemd.unit(5) before realizing the correct interpretation.
Use "might not" or "may choose not to" in these cases to make it clear
which sense we mean.
Diffstat (limited to 'man/sd_bus_set_address.xml')
-rw-r--r-- | man/sd_bus_set_address.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/sd_bus_set_address.xml b/man/sd_bus_set_address.xml index 35ebf330d0..603f153221 100644 --- a/man/sd_bus_set_address.xml +++ b/man/sd_bus_set_address.xml @@ -101,7 +101,7 @@ If specified, the identifier returned by the peer after the connection is established will be checked and the connection will be rejected in case of a mismatch.</para> - <para>Note that the addresses passed to <function>sd_bus_set_address()</function> may not be verified + <para>Note that the addresses passed to <function>sd_bus_set_address()</function> might not be verified immediately. If they are invalid, an error may be returned e.g. from a subsequent call to <citerefentry><refentrytitle>sd_bus_start</refentrytitle><manvolnum>3</manvolnum></citerefentry>. </para> |