man: mention sd_bus_message_get_creds as another way

of retrieving sd_bus_creds even though sd_bus_creds itself
contains very limited information.

diff --git a/man/sd_bus_creds_get_pid.xml b/man/sd_bus_creds_get_pid.xml
index 54714dea1db77392aed3c539354c27573342c0ab..8a193d5a59e8d43c977dba525caa34e8acfe1ae2 100644 (file)
--- a/man/sd_bus_creds_get_pid.xml
+++ b/man/sd_bus_creds_get_pid.xml
@@ -299,10 +299,12 @@
     identified by the specified PID, with
     <citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     in which case they describe the credentials of a bus peer
-    identified by the specified bus name, or with
+    identified by the specified bus name, with
     <citerefentry><refentrytitle>sd_bus_get_owner_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
     in which case they describe the credentials of the creator of a
-    bus.</para>
+    bus, or with
+    <citerefentry><refentrytitle>sd_bus_message_get_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
+    in which case they describe the credentials of the sender of the message.</para>
 
     <para><function>sd_bus_creds_get_pid()</function> will retrieve
     the PID (process identifier). Similar,