summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2015-08-17 15:56:50 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2015-08-17 16:26:43 +1000
commit5311d76ec19ce2cebf73cd4e49a58a4c08e216b5 (patch)
tree5f7508e4d5d1dc019bb96a4c586b85a0b156a434 /doc
parentf976619ebdc23a350b089de97534886fe64840b5 (diff)
doc: fix typos
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/normalization-of-relative-motion.dox6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/normalization-of-relative-motion.dox b/doc/normalization-of-relative-motion.dox
index 58ed151..31596a9 100644
--- a/doc/normalization-of-relative-motion.dox
+++ b/doc/normalization-of-relative-motion.dox
@@ -25,16 +25,16 @@ movement speed increases, acceleration is applied - at high speeds a low-dpi
device will roughly feel the same as a higher-dpi mouse.
This normalization only applies to accelerated coordinates, unaccelerated
-coordiantes are left in device-units. It is up to the caller to interpret
+coordinates are left in device-units. It is up to the caller to interpret
those coordinates correctly.
@section Normalization of touchpad coordinates
Touchpads may have a different resolution for the horizontal and vertical
-axis. Interpreting coordinates from the touchpad without taking resolutino
+axis. Interpreting coordinates from the touchpad without taking resolution
into account results in uneven motion.
-libinput scales unaccelerated touchpad motion do the resolution of the
+libinput scales unaccelerated touchpad motion to the resolution of the
touchpad's x axis, i.e. the unaccelerated value for the y axis is:
y = (x / resolution_x) * resolution_y