Update river wayland protocols

protocol/river-libinput-config-v1.xml

@@ -28,6 +28,10 @@
     documentation should be referred to for detailed information on libinput's
     behavior.
 
+    Note that the compositor will not be able to expose libinput devices through
+    this protocol when it does not have access to the hardware, for example when
+    running nested in another Wayland compositor or X11 session.
+
     This protocol is designed so that (hopefully) any backwards compatible
     change to libinput's API can be matched with a backwards compatible change
     to this protocol.
@@ -41,11 +45,6 @@
     The key words "must", "must not", "required", "shall", "shall not",
     "should", "should not", "recommended", "may", and "optional" in this
     document are to be interpreted as described in IETF RFC 2119.
-
-    Warning! The protocol described in this file is currently in the testing
-    phase. Backward compatible changes may be added together with the
-    corresponding interface version bump. Backward incompatible changes can only
-    be done by creating a new major version of the extension.
   </description>
 
   <interface name="river_libinput_config_v1" version="1">
@@ -540,7 +539,7 @@
 
     <event name="click_method_support">
       <description summary="supported click methods">
-        The click methods suppported by the device.
+        The click methods supported by the device.
       </description>
       <arg name="methods" type="uint" enum="click_methods"/>
     </event>
@@ -648,7 +647,7 @@
 
     <event name="scroll_method_support">
       <description summary="supported scroll methods">
-        The scroll methods suppported by the device.
+        The scroll methods supported by the device.
       </description>
       <arg name="methods" type="uint" enum="scroll_methods"/>
     </event>