summaryrefslogtreecommitdiff
path: root/man/sd_bus_set_watch_bind.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-06-25 14:41:05 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-06-25 14:41:44 +0200
commit4a5a01ccdd95000d60b07a9d3b1babe74598aa58 (patch)
tree3bef5e17de765004f0d84de53bd601cf76383e6a /man/sd_bus_set_watch_bind.xml
parent55cf7779f2abd3f40605d70d2a044df341339ea4 (diff)
downloadsystemd-4a5a01ccdd95000d60b07a9d3b1babe74598aa58.tar.gz
man: reword awkward sentence
Diffstat (limited to 'man/sd_bus_set_watch_bind.xml')
-rw-r--r--man/sd_bus_set_watch_bind.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/man/sd_bus_set_watch_bind.xml b/man/sd_bus_set_watch_bind.xml
index 9625652d2a..5638cdc0a6 100644
--- a/man/sd_bus_set_watch_bind.xml
+++ b/man/sd_bus_set_watch_bind.xml
@@ -56,18 +56,18 @@
<para><function>sd_bus_get_watch_bind()</function> may be used to query the current setting of this feature. It
returns zero when the feature is disabled, and positive if enabled.</para>
- <para>Note that no timeout is applied while it is waited for the socket to appear. This means that any synchronous
- remote operation (such as
+ <para>Note that no timeout is applied while we wait for the socket to appear. This means that any
+ synchronous remote operation (such as
<citerefentry><refentrytitle>sd_bus_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_add_match</refentrytitle><manvolnum>3</manvolnum></citerefentry> or
- <citerefentry><refentrytitle>sd_bus_request_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>), that is
- used on a connection with this feature enabled that is not established yet might block unbounded if the socket is
- never created. However, asynchronous remote operations (such as
+ <citerefentry><refentrytitle>sd_bus_request_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>),
+ that is used on a connection with this feature enabled that hasn't been established yet, might block
+ forever if the socket is never created. However, asynchronous remote operations (such as
<citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_bus_call_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
- <citerefentry><refentrytitle>sd_bus_add_match_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>) do
- not block in this case, and safely enqueue the requested operations to be dispatched the instant the connection is
- set up.</para>
+ <citerefentry><refentrytitle>sd_bus_add_match_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
+ do not block in this case, and safely enqueue the requested operations to be dispatched the instant the
+ connection is set up.</para>
<para>Use <citerefentry><refentrytitle>sd_bus_is_ready</refentrytitle><manvolnum>3</manvolnum></citerefentry> to
determine whether the connection is fully established, i.e. whether the peer socket has been bound, connected to