New upstream version 1.26.2 upstream/1.26.2

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/libnm/html/NMSettingConnection.html b/docs/libnm/html/NMSettingConnection.html
index 64d0303d..1cbdd134 100644
--- a/docs/libnm/html/NMSettingConnection.html
+++ b/docs/libnm/html/NMSettingConnection.html
@@ -1691,7 +1691,7 @@ nm_setting_connection_get_wait_device_timeout
 <div class="refsect3">
 <a name="nm-setting-connection-get-wait-device-timeout.returns"></a><h4>Returns</h4>
 <p> the <a class="link" href="NMSettingConnection.html#NM-SETTING-CONNECTION-WAIT-DEVICE-TIMEOUT:CAPS" title="NM_SETTING_CONNECTION_WAIT_DEVICE_TIMEOUT"><code class="literal">NM_SETTING_CONNECTION_WAIT_DEVICE_TIMEOUT</code></a> property with
-the timeout in milli seconds. -1 is the default.</p>
+the timeout in milliseconds. -1 is the default.</p>
 </div>
 <p class="since">Since: 1.20</p>
 </div>
@@ -2422,9 +2422,9 @@ be generated by <a class="link" href="libnm-nm-utils.html#nm-utils-uuid-generate
 <p>Timeout in milliseconds to wait for device at startup.
 During boot, devices may take a while to be detected by the driver.
 This property will cause to delay NetworkManager-wait-online.service
-and nm-online to give the device a chance to appear.</p>
-<p>Note that this property only works together with NMSettingConnection:interface-name
-to identify the device that will be waited for.</p>
+and nm-online to give the device a chance to appear. This works by
+waiting for the given timeout until a compatible device for the
+profile is available and managed.</p>
 <p>The value 0 means no wait time. The default value is -1, which
 currently has the same meaning as no wait time.</p>
 <p>Owner: NMSettingConnection</p>