On Fri, Aug 21, 2015 at 08:42:54AM -0700, Jason Gerecke wrote: > Signed-off-by: Jason Gerecke <[email protected]>
merged, thanks. Cheers, Peter > --- > doc/absolute-axes.dox | 2 +- > doc/faqs.dox | 2 +- > doc/gestures.dox | 2 +- > doc/palm-detection.dox | 4 ++-- > doc/reporting-bugs.dox | 2 +- > doc/seats.dox | 4 ++-- > doc/tapping.dox | 2 +- > doc/tools.dox | 4 ++-- > doc/touchpads.dox | 2 +- > 9 files changed, 12 insertions(+), 12 deletions(-) > > diff --git a/doc/absolute-axes.dox b/doc/absolute-axes.dox > index 7d205f6..664c616 100644 > --- a/doc/absolute-axes.dox > +++ b/doc/absolute-axes.dox > @@ -67,7 +67,7 @@ or height. Note that rotation applies to the device's > origin, rotation > usually requires an offset to move the coordinates back into the original > range. > > -The most comon matrices are: > +The most common matrices are: > > - 90 degree clockwise: > @f$ > diff --git a/doc/faqs.dox b/doc/faqs.dox > index 9a78dea..0e49dac 100644 > --- a/doc/faqs.dox > +++ b/doc/faqs.dox > @@ -30,7 +30,7 @@ scroll_sources. > @section faq_gpl Is libinput GPL-licensed? > > No, libinput is MIT licensed. The Linux kernel header file linux/input.h in > -libinput's tree is provded to ensure the same behavior regardless of which > +libinput's tree is provided to ensure the same behavior regardless of which > kernel version libinput is built on. It does not make libinput GPL-licensed. > > @section faq_config_options Where is the configuration stored? > diff --git a/doc/gestures.dox b/doc/gestures.dox > index a8cef36..02ef09a 100644 > --- a/doc/gestures.dox > +++ b/doc/gestures.dox > @@ -82,7 +82,7 @@ screen as well as the context of those virtual objects: > @image html touchscreen-gestures.svg "Context-sensitivity of touchscreen > gestures" > > In this example, the finger movements are identical but in the left case > -both fingers are located within the same window, thus suggesting an attemp > +both fingers are located within the same window, thus suggesting an attempt > to zoom. In the right case both fingers are located on a window border, > thus suggesting a window movement. libinput only has knowledge of the finger > coordinates (and even then only in device coordinates, not in screen > diff --git a/doc/palm-detection.dox b/doc/palm-detection.dox > index 1a5e657..d30a207 100644 > --- a/doc/palm-detection.dox > +++ b/doc/palm-detection.dox > @@ -46,10 +46,10 @@ will generate a button event for this touch. > > If a device provides a <a > href="http://en.wikipedia.org/wiki/Pointing_stick";>trackpoint</a>, it is > -usually located above the touchpad. This increases the likelyhood of > +usually located above the touchpad. This increases the likelihood of > accidental touches whenever the trackpoint is used. > > -libinput disables the touchpad whenver it detects trackpoint activity for a > +libinput disables the touchpad whenever it detects trackpoint activity for a > certain timeout until after trackpoint activity stops. Touches generated > during this timeout will not move the pointer, and touches started during > this timeout will likewise not move the pointer (allowing for a user to rest > diff --git a/doc/reporting-bugs.dox b/doc/reporting-bugs.dox > index 0755a9e..ec0ef9b 100644 > --- a/doc/reporting-bugs.dox > +++ b/doc/reporting-bugs.dox > @@ -8,7 +8,7 @@ When reporting bugs against libinput, please follow the > instructions below > and provide the required data. This will speed up triage, resulting in a > quicker bugfix. > > -First, try to identify the bugi by reproducing it reliably. The more > +First, try to identify the bug by reproducing it reliably. The more > specific a bug description is, the easier it is to fix. The @ref > libinput-debug-events helper tool can help identify whether the bug is in > libinput at all. This tool is a direct hook to libinput without a desktop > diff --git a/doc/seats.dox b/doc/seats.dox > index 5eec5de..f67de6b 100644 > --- a/doc/seats.dox > +++ b/doc/seats.dox > @@ -5,7 +5,7 @@ Each device in libinput is assigned to one seat. > A seat has two identifiers, the physical name and the logical name. The > physical name is summarized as the list of devices a process on the same > physical seat has access to. The logical seat name is the seat name for a > -logical group of devices. A compositor may use that to create additonal > +logical group of devices. A compositor may use that to create additional > seats as independent device sets. Alternatively, a compositor may limit > itself to a single logical seat, leaving a second compositor to manage > devices on the other logical seats. > @@ -32,7 +32,7 @@ libinput_seat, all other devices reference their own > respective seats. > > @section seats_and_features The effect of seat assignment > > -A logical set is interprested as a group of devices that usually belong to a > +A logical set is interpreted as a group of devices that usually belong to a > single user that interacts with a computer. Thus, the devices are > semantically related. This means for devices within the same logical seat: > > diff --git a/doc/tapping.dox b/doc/tapping.dox > index 483219a..e704400 100644 > --- a/doc/tapping.dox > +++ b/doc/tapping.dox > @@ -40,7 +40,7 @@ disabled with > libinput_device_config_tap_set_drag_lock_enabled(). > The above diagram explains the process, a tap (a) followed by a finger held > down (b) starts the drag process and logically holds the left mouse button > down. A movement of the finger (c) will drag the selected item until the > -finger is relased (e). If needed and drag lock is enabled, the finger's > +finger is released (e). If needed and drag lock is enabled, the finger's > position can be reset by lifting and quickly setting it down again on the > touchpad (d). This will be interpreted as continuing move and is especially > useful on small touchpads or with slow pointer acceleration. > diff --git a/doc/tools.dox b/doc/tools.dox > index 2bf0793..7fe1e07 100644 > --- a/doc/tools.dox > +++ b/doc/tools.dox > @@ -8,7 +8,7 @@ tools are usually installed, others are @ref developer_tools > only. > > libinput ships with two tools to gather information about devices: > @ref libinput-list-devices and @ref libinput-debug-events. Both tools must > -be run as root to have acess to the kernel's @c /dev/input/event* device > +be run as root to have access to the kernel's @c /dev/input/event* device > files. > > @subsection libinput-list-devices > @@ -97,6 +97,6 @@ $ sudo ./tools/event-gui > See the @c --help output for information about the available options. > > @note The @c --grab flag puts an exclusive @c EVIOCGRAB on the device to > -avoid interference with the desktiop while testing. > +avoid interference with the desktop while testing. > > */ > diff --git a/doc/touchpads.dox b/doc/touchpads.dox > index 401f16a..91a9b6a 100644 > --- a/doc/touchpads.dox > +++ b/doc/touchpads.dox > @@ -130,7 +130,7 @@ located underneath the keyboard, accidental palm touches > are a non-issue. > > Pressure is usually directly related to contact area. Human fingers flatten > out as the pressure on the pad increases, resulting in a bigger contact area > -and the firmware then calculates that back into a ressure reading. > +and the firmware then calculates that back into a pressure reading. > > libinput uses pressure to detect accidental palm contact and thumbs, though > pressure data is often device-specific and unreliable. > -- > 2.5.0 > _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
