X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_journal_seek_head.xml;h=d24b2f30ee233dfdd9caf652abd8b19000ffa803;hp=b6a9a731c115a06ad8ab5321f0652e7026bcab18;hb=2ca0435be9359bde3020eeb528c2a6d72ac1e0b0;hpb=639a6a2529dd5a3109b998ccb44fb75b97525e13

diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml
index b6a9a731c..d24b2f30e 100644
--- a/man/sd_journal_seek_head.xml
+++ b/man/sd_journal_seek_head.xml
@@ -92,7 +92,7 @@
 
                 <para><function>sd_journal_seek_head()</function>
                 seeks to the beginning of the journal, i.e. the oldest
-                avilable entry.</para>
+                available entry.</para>
 
                 <para>Similar,
                 <function>sd_journal_seek_tail()</function> may be
@@ -101,21 +101,26 @@
 
                 <para><function>sd_journal_seek_monotonic_usec()</function>
                 seeks to the entry with the specified monotonic
-                timestamp, i.e. CLOCK_MONOOTONIC. Since monotonic time
+                timestamp, i.e. CLOCK_MONOTONIC. Since monotonic time
                 restarts on every reboot a boot ID needs to be
                 specified as well.</para>
 
                 <para><function>sd_journal_seek_realtime_usec()</function>
                 seeks to the entry with the specified realtime
                 (wallclock) timestamp, i.e. CLOCK_REALTIME. Note that
-                the realtime clock is not necessary monotonic. If a
+                the realtime clock is not necessarily monotonic. If a
                 realtime timestamp is ambiguous it is not defined
-                which position is seeked to.</para>
+                which position is sought to.</para>
 
                 <para><function>sd_journal_seek_cursor()</function>
                 seeks to the entry located at the specified cursor
                 string. For details on cursors see
-                <citerefentry><refentrytitle>sd_journal_get_cursor</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
+                <citerefentry><refentrytitle>sd_journal_get_cursor</refentrytitle><manvolnum>3</manvolnum></citerefentry>. If
+                no entry matching the specified cursor is found the
+                call will seek to the next closest entry (in terms of
+                time) instead. To verify whether the newly selected
+                entry actually matches the cursor use
+                <citerefentry><refentrytitle>sd_journal_test_cursor</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
                 <para>Note that these calls do not actually make any
                 entry the new current entry, this needs to be done in
@@ -125,12 +130,12 @@
                 may be retrieved via
                 <citerefentry><refentrytitle>sd_journal_get_data</refentrytitle><manvolnum>3</manvolnum></citerefentry>. If
                 no entry exists that matches exactly the specified
-                seek address the next closest is seeked to. If
+                seek address the next closest is sought to. If
                 <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-                is used the closest following entry will be seeked to,
+                is used the closest following entry will be sought to,
                 if
                 <citerefentry><refentrytitle>sd_journal_previous</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-                is used the closest preceeding entry is seeked
+                is used the closest preceding entry is sought
                 to.</para>
         </refsect1>