diff options
author | Jan Engelhardt <jengelh@inai.de> | 2013-09-12 21:12:49 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2013-09-12 22:09:57 +0200 |
commit | 79640424059328268b9fb6c5fa8eb777b27a177e (patch) | |
tree | e3579216d1afd438e667044869dcdf9c732ef18c /man/sd_journal_seek_head.xml | |
parent | 982e44dbc3e70c97e83464a30354b80973d52b41 (diff) |
man: wording and grammar updates
This is a recurring submission and includes corrections to various
issue spotted. I guess I can just skip over reporting ubiquitous
comma placement fixes…
Highligts in this particular commit:
- the "unsigned" type qualifier is completed to form a full type
"unsigned int"
- alphabetic -> lexicographic (that way we automatically define how
numbers get sorted)
Diffstat (limited to 'man/sd_journal_seek_head.xml')
-rw-r--r-- | man/sd_journal_seek_head.xml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml index c4e64096e1..03de30a383 100644 --- 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 |