man: document a tiny bit better what udev_device_get_is_initialized() actually returns

diff --git a/man/udev_device_get_syspath.xml b/man/udev_device_get_syspath.xml
index b54749ed56deb7e4d428306786fcb4fcca3a6e8c..014f43b21cefa40e527b44aca4db110fcc4efe96 100644 (file)
--- a/man/udev_device_get_syspath.xml
+++ b/man/udev_device_get_syspath.xml
@@ -184,10 +184,10 @@
     to such a parent device. On failure, <constant>NULL</constant>
     is returned.</para>
 
-    <para>On success, <function>udev_device_get_is_initialized()</function>
-    returns either <constant>1</constant> or <constant>0</constant>,
-    depending on whether the passed device is initialized or not. On
-    failure, a negative error code is returned.</para>
+    <para>On success, <function>udev_device_get_is_initialized()</function> returns either <constant>1</constant> or
+    <constant>0</constant>, depending on whether the passed device has already been initialized by udev or not. On
+    failure, a negative error code is returned. Note that devices for which no udev rules are defined are never
+    reported initialized.</para>
   </refsect1>
 
   <refsect1>