X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_journal_seek_head.xml;h=03de30a383c0570e763cf8c7f0f9bce0e87234b8;hb=fb1316462952d17d6ebf19c3f093b730c13016a7;hp=c4e64096e177b349ffe0a1695d13d968d0de18af;hpb=1e158d273bb63883566358cbb886cd4167421df6;p=elogind.git
diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml
index c4e64096e..03de30a38 100644
--- a/man/sd_journal_seek_head.xml
+++ b/man/sd_journal_seek_head.xml
@@ -111,30 +111,30 @@
(wallclock) timestamp,
i.e. CLOCK_REALTIME. 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.
sd_journal_seek_cursor()
seeks to the entry located at the specified cursor
- string. For details on cursors see
+ string. For details on cursors, see
sd_journal_get_cursor3. 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
sd_journal_test_cursor3.
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
sd_journal_next3
- invocation (or a similar call). Only then entry data
+ invocation (or a similar call). Only then, entry data
may be retrieved via
sd_journal_get_data3. 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
sd_journal_next3
- is used the closest following entry will be sought to,
+ is used, the closest following entry will be sought to,
if
sd_journal_previous3
is used the closest preceding entry is sought