bus: introduce concept of a default bus for each thread and make use of it everywhere

[elogind.git] / man / sd_journal_seek_head.xml

diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml
index c4e64096e177b349ffe0a1695d13d968d0de18af..03de30a383c0570e763cf8c7f0f9bce0e87234b8 100644 (file)
--- a/man/sd_journal_seek_head.xml
+++ b/man/sd_journal_seek_head.xml
@@ -111,30 +111,30 @@
                 (wallclock) timestamp,
                 i.e. <constant>CLOCK_REALTIME</constant>. Note that
                 the realtime clock is not necessarily monotonic. If a
-                realtime timestamp is ambiguous it is not defined
+                realtime timestamp is ambiguous, it is not defined
                 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
+                string. For details on cursors, see
                 <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
+                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
                 a separate step with a subsequent
                 <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-                invocation (or a similar call). Only then entry data
+                invocation (or a similar call). Only then, entry data
                 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 sought 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 sought 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 preceding entry is sought