ext-action-binder: fix typos

Signed-off-by: Anna (navi) Figueiredo Gomes <navi@vlhl.dev>

1 files changed, 14 insertions, 14 deletions

diff --git a/staging/ext-action-binder/ext-action-binder-v1.xml b/staging/ext-action-binder/ext-action-binder-v1.xml
index 5a8d513..fd29297 100644
--- a/staging/ext-action-binder/ext-action-binder-v1.xml
+++ b/staging/ext-action-binder/ext-action-binder-v1.xml
@@ -46,7 +46,7 @@
       Here are some examples of dispatching choice: all applications, last
       focused, user-defined preference order, latest fullscreened application.
 
-      This interface is exposed as global
+      This interface is exposed as global.
     </description>
 
     <request name="destroy" type="destructor">
@@ -138,7 +138,7 @@
       <description summary="sets a target seat">
         This setting is optional.
 
-        Attempting to send this request twice or after the binding was bound raises an already_set error
+        Attempting to send this request twice or after the binding was bound raises an already_set error.
       </description>
       <arg name="seat" type="object" interface="wl_seat" summary="target seat"/>
     </request>
@@ -147,26 +147,26 @@
       <description summary="sets the machine-readable trigger of a binding">
         This setting is optional.
         The trigger is a suggestion to the compositor, and the action should not rely
-        to being set to that specific trigger.
+        on being set to that specific trigger.
 
         The client does not know which trigger was actually set, but when a binding is
-        bound, it recieves from the compositor a human readable string describing the trigger,
+        bound, it receives from the compositor a human readable string describing the trigger,
         if any, so it could show it in a ui.
 
         The trigger format is split into two fields, what kind of device triggers it, and a
         general trigger string.
 
-        as of version 1 of this protocol, the following kinds are defined:
-        "sym": trigger is a combo of XKB key names
+        As of version 1 of this protocol, the following kinds are defined:
+        "sym": trigger is a combo of XKB key names.
         "mouse": trigger is button[1-9], mapped to their x11 values, (1=left, 2=middle, 3=right,
-        4=scroll up, 5=scroll down, 6=scroll left, 7=scroll right, 8=back, 9=forward)
-        "switch": trigger on the format switch:state, where "lid" and "tablet" are valid switches
+        4=scroll up, 5=scroll down, 6=scroll left, 7=scroll right, 8=back, 9=forward).
+        "switch": trigger on the format switch:state, where "lid" and "tablet" are valid switches.
         "gesture": trigger on the format gesture[:fingers][:direction] with the following gestures:
-        hold: 1-5 fingers, no direction
-        swipe: 3-5 fingers, up, down, left or right
-        pinch: 2-5 fingers, all above, inward, outward, clockwise, counterclockwise
+        hold: 1-5 fingers, no direction.
+        swipe: 3-5 fingers, up, down, left or right.
+        pinch: 2-5 fingers, all above, inward, outward, clockwise, counterclockwise.
 
-        Attempting to send this request twice or after the binding was bound raises an already_set error
+        Attempting to send this request twice or after the binding was bound raises an already_set error.
       </description>
       <arg name="kind" type="string" summary="what category of trigger it fits in"/>
       <arg name="trigger" type="string" summary="a trigger that the client would like to trigger the action"/>
@@ -181,10 +181,10 @@
 
     <event name="rejected">
       <description summary="the compositor rejected the binding">
-        Sent after the event was processed, and got rejected.
+        Sent after the event was processed and got rejected,
         or at any time should the compositor want to remove the binding.
         The compositor will send no further events after this event.
-        The client should destroy the resource at this point.
+        The client should destroy the object at this point.
       </description>
     </event>