summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2014-04-07 14:21:27 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2014-04-07 14:23:21 +1000
commitbe87068a9bbcfefef822a06640f4a931389057d6 (patch)
tree5a40603bd9c76524ed5751e03364e2796aedf5b8
parent6cbf971b3969de37a2a8e5c6cb02a0648210a6af (diff)
downloadlibevdev-be87068a9bbcfefef822a06640f4a931389057d6.tar.gz
Fix a typo, add a @ref in the documentation
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-rw-r--r--libevdev/libevdev.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/libevdev/libevdev.h b/libevdev/libevdev.h
index aa7b90d..bf221fb 100644
--- a/libevdev/libevdev.h
+++ b/libevdev/libevdev.h
@@ -165,7 +165,7 @@ extern "C" {
* The kernel sends evdev events separated by an event of type EV_SYN and
* code SYN_REPORT. Such an event marks the end of a frame of hardware
* events. The number of events between SYN_REPORT events is arbitrary and
- * depends on the hardware. And example event sequence may look like this:
+ * depends on the hardware. An example event sequence may look like this:
* @code
EV_ABS ABS_X 9
EV_ABS ABS_Y 8
@@ -218,7 +218,7 @@ extern "C" {
* libevdev simplifies this approach: if the state of the device has
* changed, libevdev generates an event for each code with the new value and
* passes it to the caller during libevdev_next_event() if
- * LIBEVDEV_READ_FLAG_SYNC is set.
+ * @ref LIBEVDEV_READ_FLAG_SYNC is set.
*
* For events of type EV_ABS and an event code less than ABS_MT_SLOT, the
* handling of state changes is as described above. For events between