X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_journal_get_realtime_usec.xml;h=515932c6d89fcdf4d8d0ceff4a20d725d1b94a72;hp=bebf4f5a3ce1a2dde1d911c04f2576d377465935;hb=735248643920eadf021526714c1eb67518086e8d;hpb=7a8a6e88545bf22909941c9b022873709a1a1c9e

diff --git a/man/sd_journal_get_realtime_usec.xml b/man/sd_journal_get_realtime_usec.xml
index bebf4f5a3..515932c6d 100644
--- a/man/sd_journal_get_realtime_usec.xml
+++ b/man/sd_journal_get_realtime_usec.xml
@@ -72,15 +72,15 @@
                 <title>Description</title>
 
                 <para><function>sd_journal_get_realtime_usec()</function>
-                gets the realtime (wallclock) timestamp of the the
+                gets the realtime (wallclock) timestamp of the
                 current journal entry.  It takes two arguments: the
                 journal context object and a pointer to a 64 Bit
                 unsigned integer to store the timestamp in. The
                 timestamp is in microseconds since the epoch,
                 i.e. CLOCK_REALTIME.</para>
 
-                <para><function>sd_journal_get_realtime_usec()</function>
-                gets the monotonic timestamp of the the current
+                <para><function>sd_journal_get_monotonic_usec()</function>
+                gets the monotonic timestamp of the current
                 journal entry.  It takes three arguments: the journal
                 context object, a pointer to a 64 Bit unsigned integer
                 to store the timestamp in as well as a 128 Bit ID
@@ -89,7 +89,7 @@
                 the specific boot, i.e. CLOCK_MONOTONIC. Since the
                 monotonic clock begins new with every reboot it only
                 defines a well-defined point in time when used
-                together with a identifier identifying the boot, see
+                together with an identifier identifying the boot, see
                 <citerefentry><refentrytitle>sd_id128_get_boot</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                 for more information. If the boot ID parameter is
                 passed NULL the function will fail if the monotonic
@@ -99,7 +99,7 @@
                 <para>Note that these functions will not work before
                 <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                 (or related call) has been called at least
-                once.</para>
+                once, in order to position the read pointer at a valid entry.</para>
         </refsect1>
 
         <refsect1>
@@ -138,7 +138,8 @@
                         <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
                         <citerefentry><refentrytitle>sd_journal_get_data</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
                         <citerefentry><refentrytitle>sd_id128_get_boot</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
-                        <citerefentry><refentrytitle>clock_gettime</refentrytitle><manvolnum>2</manvolnum></citerefentry>
+                        <citerefentry><refentrytitle>clock_gettime</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
+                        <citerefentry><refentrytitle>sd_journal_get_cutoff_realtime_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                 </para>
         </refsect1>