fdo-mirrors/wayland-protocols
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland-protocols.git synced 2026-05-08 20:38:03 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

relative-pointer: Correct spelling error, one capitalization, and minor space

Browse source 
Downcase the protocol description summary.
Adjust two double-spaces to one, like the rest of the content.

Signed-off-by: Yong Bakos <ybakos@humanoriented.com>
Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
This commit is contained in:
Yong Bakos 2016-04-11 17:22:58 -05:00 • committed by Bryce Harrington
parent 4e7b2fb4da
commit fc2889ba01
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
unstable/relative-pointer/relative-pointer-unstable-v1.xml
View file

@ -25,7 +25,7 @@
DEALINGS IN THE SOFTWARE.
</copyright>
<description summary="Protocol for relative pointer motion events">
<description summary="protocol for relative pointer motion events">
This protocol specifies a set of interfaces used for making clients able to
receive relative pointer events not obstructed by barriers (such as the
monitor edge or other pointer barriers).
@ -42,9 +42,9 @@
Warning! The protocol described in this file is experimental and backward
incompatible changes may be made. Backward compatible changes may be added
together with the corresponding interface version bump. Backward
together with the corresponding interface version bump. Backward
incompatible changes are done by bumping the version number in the protocol
and interface names and resetting the interface version. Once the protocol
and interface names and resetting the interface version. Once the protocol
is to be declared stable, the 'z' prefix and the version number in the
protocol and interface names are removed and the interface version number is
reset.
@ -111,7 +111,7 @@
Relative motions are not coupled to wl_pointer.motion events, and can be
sent in combination with such events, but also independently. There may
also be scenarious where wl_pointer.motion is sent, but there is no
also be scenarios where wl_pointer.motion is sent, but there is no
relative motion. The order of an absolute and relative motion event
originating from the same physical motion is not guaranteed.