treewide: fix typos

Signed-off-by: Torstein Husebø <torstein@huseboe.net>

completion/zsh/_libinput

@@ -196,7 +196,7 @@ __all_seats()
 		'--help[Show help message and exit]' \
 		'--all[Record all /dev/input/event* devices available on the system]' \
 		'--autorestart=[Terminate the current recording after s seconds of device inactivity]' \
-		{-o+,--output=}'[Speficy the output file to use]:file:_files -g "*.yml"' \
+		{-o+,--output=}'[Specify the output file to use]:file:_files -g "*.yml"' \
 		'--multiple[Record multiple devices at once]' \
 		'--show-keycodes[Show keycodes as-is in the recording]' \
 		'--with-libinput[Record libinput events alongside device events]' \

doc/user/device-configuration-via-udev.rst

@@ -150,7 +150,7 @@ The property **LIBINPUT_MODEL_LENOVO_X220_TOUCHPAD_FW81** may be set by a
 user in a local hwdb file. This property designates the touchpad on a Lenovo
 x220 with a touchpad firmware version 8.1. When this firmware version is
 installed, the touchpad is imprecise. The touchpad device does not send
-continuos x/y axis position updates, a behavior also observed on its
+continuous x/y axis position updates, a behavior also observed on its
 successor model, the Lenovo x230 which has the same firmware version. If the
 above property is set, libinput adjusts its behavior to better suit this
 particular model.
@@ -263,4 +263,4 @@ Modifying the hwdb
              device-specific quirks must go in to the :ref:`device-quirks` system.
 
 For information about older libinput versions, please see the documentation
-for your version avaialable in: https://wayland.freedesktop.org/libinput/doc/
+for your version available in: https://wayland.freedesktop.org/libinput/doc/

doc/user/device-quirks.rst

@@ -6,7 +6,7 @@ Device quirks
 
 libinput requires extra information from devices that is not always readily
 available. For example, some touchpads are known to have jumping cursors
-under specific conditions. libinput ships a set of files containting the
+under specific conditions. libinput ships a set of files containing the
 so-called model quirks to provide that information. Model quirks are usually
 installed under ``/usr/share/libinput/<filename>.quirks`` and are standard
 ``.ini`` files. A file may contain multiple section headers (``[some

doc/user/faqs.rst

@@ -218,7 +218,7 @@ Why don't synclient and syndaemon work with libinput?
 
 Synclient and syndaemon rely on X input device properties that are specific
 to the xf86-input-synaptics X.Org input driver. Both were written when the
-synaptics driver was the only commmon touchpad driver in existence. They
+synaptics driver was the only common touchpad driver in existence. They
 assume that if the properties aren't available, no touchpad is available
 either. The xf86-input-libinput X.Org input driver does not export these
 driver-specific properties, synclient/syndaemon will thus not detect the

doc/user/features.rst

@@ -5,7 +5,7 @@ libinput Features
 ==============================================================================
 
 Below is a list of features supported by libinput. The availability of
-features usually depends on the device type and a device's capabilties.
+features usually depends on the device type and a device's capabilities.
 Not all features are user-configurable, some rely on :ref:`device-quirks`
 to be useful.
 

doc/user/reporting-bugs.rst

@@ -305,7 +305,7 @@ updated its package accordingly.
 
 Whether the bug fix ends up in your distribution depends on a number of
 things. Any given bug fix **may** be cherry-picked into the current stable
-branch, depending on its severity, impact, and likelyhood to cause
+branch, depending on its severity, impact, and likelihood to cause
 regressions. Once cherry-picked it will land in the next stable branch
 release. These are usually a few weeks apart.
 

doc/user/switches.rst

@@ -28,14 +28,14 @@ The evdev event code ``EV_SW`` ``SW_LID`` is provided as
 the device is disabled while the lid is logically closed. This is to avoid
 ghost touches that can be caused by interference with touchpads and the
 closed lid. The touchpad is automatically re-enabled whenever the lid is
-openend.
+opened.
 
 This handling of lid switches is transparent to the user, no notifications
 are sent and the device appears as enabled at all times.
 
 On some devices, the device's lid state does not always reflect the physical
 state and the lid state may report as closed even when the lid is physically
-open. libinput employs some heuristics to detect user input (specificially
+open. libinput employs some heuristics to detect user input (specifically
 typing) to re-enable the touchpad on those devices. Where input is detected,
 libinput updates the lid status of the kernel device so other consumers of
 the kernel events also get the accurate state.

doc/user/trackpoint-configuration.rst

@@ -20,7 +20,7 @@ User-specific preferences can be adjusted with the
 The magic trackpoint multiplier
 ------------------------------------------------------------------------------
 
-To accomodate for the wildly different input data on trackpoint, libinput
+To accommodate for the wildly different input data on trackpoint, libinput
 uses a multiplier that is applied to input deltas. Trackpoints that send
 comparatively high deltas can be "slowed down", trackpoints that send low
 deltas can be "sped up" to match the expected range. The actual acceleration

doc/user/trackpoints.rst

@@ -5,7 +5,7 @@ Trackpoints and Pointing Sticks
 ==============================================================================
 
 This page provides an overview of trackpoint handling in libinput, also
-refered to as Pointing Stick or Trackstick. The device itself is usually a
+referred to as Pointing Stick or Trackstick. The device itself is usually a
 round plastic stick between the G, H and B keys with a set of buttons below
 the space bar.
 

quirks/50-system-dell.quirks

@@ -11,7 +11,7 @@ MatchUdevType=touchpad
 MatchDMIModalias=dmi:*svnDellInc.:*
 AttrMscTimestamp=watch
 
-[Dell Lattitude E6220 Touchpad]
+[Dell Latitude E6220 Touchpad]
 MatchName=*AlpsPS/2 ALPS GlidePoint
 MatchDMIModalias=dmi:*svnDellInc.:pnLatitudeE6220:*
 AttrPressureRange=100:90

quirks/50-system-hp.quirks

@@ -14,7 +14,7 @@ MatchName=*SynPS/2 Synaptics TouchPad
 MatchDMIModalias=dmi:*svnHewlett-Packard:*pnHPCompaq8510w*
 AttrEventCodeDisable=BTN_TOOL_DOUBLETAP;BTN_TOOL_TRIPLETAP;
 
-[HP Pavillion dmi4]
+[HP Pavilion dmi4]
 MatchName=*SynPS/2 Synaptics TouchPad
 MatchDMIModalias=dmi:*svnHewlett-Packard:*pnHPPaviliondm4NotebookPC*
 ModelHPPavilionDM4Touchpad=1
@@ -46,7 +46,7 @@ MatchName=*Cypress APA Trackpad *cyapa*
 MatchDMIModalias=dmi:*svnHewlett-Packard*:pnFalco*
 AttrPressureRange=12:8
 
-[HP Spectre x360 Convertable 15-bl1xx]
+[HP Spectre x360 Convertible 15-bl1xx]
 MatchUdevType=touchpad
 MatchName=*SynPS/2 Synaptics TouchPad
 MatchDMIModalias=dmi:*svnHP:pnHPSpectrex360Convertible15-bl1XX:*
@@ -54,7 +54,7 @@ AttrPressureRange=55:40
 AttrThumbPressureThreshold=90
 AttrPalmPressureThreshold=100
 
-[HP Spectre x360 Convertable 15-ch0xx]
+[HP Spectre x360 Convertible 15-ch0xx]
 MatchUdevType=touchpad
 MatchName=*SynPS/2 Synaptics TouchPad
 MatchDMIModalias=dmi:*svnHP:pnHPSpectrex360Convertible15-ch0xx:*

src/evdev-mt-touchpad-tap.c

@@ -1442,7 +1442,7 @@ tp_tap_handle_state(struct tp_dispatch *tp, uint64_t time)
 		if (t->tap.is_thumb)
 			continue;
 
-		/* A palm tap needs to be properly relased because we might
+		/* A palm tap needs to be properly released because we might
 		 * be who-knows-where in the state machine. Otherwise, we
 		 * ignore any event from it.
 		 */

src/evdev-mt-touchpad.c

@@ -153,7 +153,7 @@ tp_motion_history_push(struct tp_touch *t)
  * human can move like that within thresholds.
  *
  * We encode left moves as zeroes, and right as ones. We also drop
- * the array to all zeroes when contraints are not satisfied. Then we
+ * the array to all zeroes when constraints are not satisfied. Then we
  * search for the pattern {1,0,1}. It can't match {Left, Right, Left},
  * but it does match {Left, Right, Left, Right}, so it's okay.
  *
@@ -611,7 +611,7 @@ tp_restore_synaptics_touches(struct tp_dispatch *tp,
 	    (tp->nfingers_down == tp->num_slots && nfake_touches == tp->num_slots))
 		return;
 
-	/* Synaptics devices may end touch 2 on transition to/fro
+	/* Synaptics devices may end touch 2 on transition to/from
 	 * BTN_TOOL_TRIPLETAP and start it again on the next frame with
 	 * different coordinates (bz#91352, gitlab#434). We search the
 	 * touches we have, if there is one that has just ended despite us
@@ -1639,7 +1639,7 @@ tp_process_msc_timestamp(struct tp_dispatch *tp, uint64_t time)
 		   SYN_REPORT +8ms
 
 	   Our approach is to detect the 0 timestamp, check the interval on
-	   the next event and then calculate the movement for one fictious
+	   the next event and then calculate the movement for one fictitious
 	   event instead, swallowing all other movements. So if the time
 	   delta is equivalent to 10 events and the movement is x, we
 	   instead pretend there was movement of x/10.
@@ -2973,7 +2973,7 @@ tp_init_accel(struct tp_dispatch *tp, enum libinput_config_accel_profile which)
 	 * Normalize motion events to the default mouse DPI as base
 	 * (unaccelerated) speed. This also evens out any differences in x
 	 * and y resolution, so that a circle on the
-	 * touchpad does not turn into an elipse on the screen.
+	 * touchpad does not turn into an ellipse on the screen.
 	 */
 	tp->accel.x_scale_coeff = (DEFAULT_MOUSE_DPI/25.4) / res_x;
 	tp->accel.y_scale_coeff = (DEFAULT_MOUSE_DPI/25.4) / res_y;

src/evdev-tablet.c

@@ -365,7 +365,7 @@ normalize_pressure(const struct input_absinfo *absinfo,
 	 *
 	 * This means that there is a small range (lower-upper) where
 	 * different physical pressure (default: 1-5%) result in the same
-	 * logical pressure. This is, hopefully, not noticable.
+	 * logical pressure. This is, hopefully, not noticeable.
 	 *
 	 * Note that that lower-upper range gives us a negative pressure, so
 	 * we have to clip to 0 for those.
@@ -1707,7 +1707,7 @@ tablet_send_events(struct tablet_dispatch *tablet,
 		 */
 		axes = tablet->axes;
 
-		/* Dont' send an axis event, but we may have a tip event
+		/* Don't send an axis event, but we may have a tip event
 		 * update */
 		tablet_unset_status(tablet, TABLET_AXES_UPDATED);
 	} else {

src/filter-touchpad-x230.c

@@ -112,7 +112,7 @@ calculate_acceleration(struct pointer_accelerator_x230 *accel,
 {
 	double factor;
 
-	/* Use Simpson's rule to calculate the avarage acceleration between
+	/* Use Simpson's rule to calculate the average acceleration between
 	 * the previous motion and the most recent. */
 	factor = acceleration_profile(accel, data, velocity, time);
 	factor += acceleration_profile(accel, data, last_velocity, time);

src/filter.c

@@ -285,7 +285,7 @@ calculate_acceleration_simpsons(struct motion_filter *filter,
 {
 	double factor;
 
-	/* Use Simpson's rule to calculate the avarage acceleration between
+	/* Use Simpson's rule to calculate the average acceleration between
 	 * the previous motion and the most recent. */
 	factor = profile(filter, data, velocity, time);
 	factor += profile(filter, data, last_velocity, time);

src/filter.h

@@ -50,7 +50,7 @@ struct motion_filter;
  * @param time The time of the delta
  *
  * @return A set of normalized coordinates that can be used for pixel
- * movement. The normalized coordiantes are scaled to the default dpi range,
+ * movement. The normalized coordinates are scaled to the default dpi range,
  * i.e. regardless of the resolution of the underlying device, the returned
  * values always reflect a 1000dpi mouse.
  *

src/util-prop-parsers.c

@@ -249,7 +249,7 @@ parse_tpkbcombo_layout_poperty(const char *prop,
 
 /**
  * Parses a string of the format "a:b" where both a and b must be integer
- * numbers and a > b. Also allowed is the special string vaule "none" which
+ * numbers and a > b. Also allowed is the special string value "none" which
  * amounts to unsetting the property.
  *
  * @param prop The value of the property

src/util-strings.c

@@ -115,7 +115,7 @@ strv_from_string(const char *in, const char *separators)
  * An empty strv ([NULL]) returns NULL, same for passing NULL as either
  * argument.
  *
- * @param strv Input string arrray
+ * @param strv Input string array
  * @param joiner Joiner between the elements in the final string
  *
  * @return A null-terminated string joining all elements

test/litest.c

@@ -1426,7 +1426,7 @@ litest_install_model_quirks(struct list *created_files_list)
 				false);
 	list_insert(created_files_list, &file->link);
 
-	/* Ony install the litest device rule when we're running as system
+	/* Only install the litest device rule when we're running as system
 	 * test suite, we expect the others to be in place already */
 	if (use_system_rules_quirks)
 		return;

test/test-device.c

@@ -164,7 +164,7 @@ START_TEST(device_disable)
 	ck_assert_int_eq(status, LIBINPUT_CONFIG_STATUS_SUCCESS);
 	litest_assert_empty_queue(li);
 
-	/* event from renabled device */
+	/* event from re-enabled device */
 	litest_event(dev, EV_REL, REL_X, 10);
 	litest_event(dev, EV_SYN, SYN_REPORT, 0);
 

test/test-misc.c

@@ -771,7 +771,7 @@ START_TEST(timer_flush)
 	libinput_dispatch(li);
 	litest_assert_only_typed_events(li, LIBINPUT_EVENT_KEYBOARD_KEY);
 
-	/* Ingore 'timer offset negative' warnings */
+	/* Ignore 'timer offset negative' warnings */
 	litest_disable_log_handler(li);
 
 	/* now mess with the timing

test/test-touch.c

@@ -987,7 +987,7 @@ START_TEST(touch_release_on_unplug)
 	litest_touch_move_to(dev, 0, 50, 50, 70, 70, 10);
 	litest_drain_events(li);
 
-	/* Touch is still down when device is removed, espect a release */
+	/* Touch is still down when device is removed, expect a release */
 	litest_delete_device(dev);
 	libinput_dispatch(li);
 

tools/libinput-analyze-per-slot-delta.py

@@ -150,8 +150,8 @@ def main(argv):
     parser.add_argument("--use-absolute", action='store_true', help="Use absolute coordinates, not deltas")
     parser.add_argument("path", metavar="recording",
                         nargs=1, help="Path to libinput-record YAML file")
-    parser.add_argument("--threshold", type=float, default=None, help="Mark any delta above this treshold")
+    parser.add_argument("--threshold", type=float, default=None, help="Mark any delta above this threshold")
-    parser.add_argument("--ignore-below", type=float, default=None, help="Ignore any delta below this theshold")
+    parser.add_argument("--ignore-below", type=float, default=None, help="Ignore any delta below this threshold")
     args = parser.parse_args()
 
     if not sys.stdout.isatty():

tools/libinput-measure-touchpad-size.man

@@ -24,7 +24,7 @@ This tool usually needs to be run as root to have access to the
 /dev/input/eventX nodes.
 .SH OPTIONS
 This tool must be provided the physical dimensions of the device in mm.
-For example, if your touchpad is 100mm wide and 55mm heigh, run this tool as
+For example, if your touchpad is 100mm wide and 55mm high, run this tool as
 .B libinput measure touchpad-size 100x55
 .PP
 If a device node is given, this tool opens that device node. Otherwise, this

tools/libinput-measure-touchpad-tap.man

@@ -66,7 +66,7 @@ prints comments at the top of the file to describe each column.
 .B WARNING:
 The data contained in the output is grouped by different sort orders. For
 example, the first few columns may list tap information in the 'natural'
-sort order (i.e. as they occured), the data in the next few columns may list
+sort order (i.e. as they occurred), the data in the next few columns may list
 tap information sorted by the delta time between touch down and touch up.
 Comparing columns across these group boundaries will compare data of two
 different touch points and result in invalid analysis.

tools/libinput-measure-touchpad-tap.py

@@ -189,7 +189,7 @@ class Device(libevdev.Device):
               #    point within each group. Comparing data across groups
               #    will result in invalid analysis.
               # Columns (1-indexed):
-              # Group 1, sorted by time of occurence
+              # Group 1, sorted by time of occurrence
               #  1: touch down time in ms, offset by first event
               #  2: touch up time in ms, offset by first event
               #  3: time delta in ms);