diff --git a/man/NetworkManager-wait-online.service.xml b/man/NetworkManager-wait-online.service.xml
index d061643c3..9bc947e54 100644
--- a/man/NetworkManager-wait-online.service.xml
+++ b/man/NetworkManager-wait-online.service.xml
@@ -95,6 +95,11 @@
setting). While trying and retrying, NetworkManager is busy until all
profiles and devices either reached an activated or disconnected state
and no further events are expected.
+
+
+ Basically, as long as there are devices and connections in activating
+ state visible with nmcli device and nmcli connection,
+ startup is still pending.
@@ -120,11 +125,29 @@
This is a configuration error.
+
+
+ Dispatcher scripts for the "pre-up" event run at a late stage during activation
+ of a profile. These scripts block the activation for when NetworkManager considers
+ the profile fully activated.
+ See also NetworkManager-dispatcher8
+ for details.
+
+
+
+
+ The connection property connection.wait-activation-delay also
+ adds an additional delay during activation and delays startup complete. This is to
+ workaround certain cases where a device is known to not be ready for a certain
+ amount of time.
+
+
The property connection.wait-device-timeout of the connection
profiles waits until the waited devices appear. This is useful if the driver
- takes a longer time to detect the networking interfaces.
+ takes a longer time to detect the networking interfaces. Similar with the
+ connection.gateway-ping-timeout property.