git.lucas.co / cce-compositor
Wayland compositor (wlroots)
git clone https://git.lucas.co/cce-compositor.git

commit91f9feed91c3b969db8b46edf2727a9d392aee76
parent1d222f913e
authorIsaac Freund <[email protected]>
date2026-04-13 13:40
protocol: fix documentation typos

 protocol/river-window-management-v1.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/protocol/river-window-management-v1.xml b/protocol/river-window-management-v1.xml
index 64bfa58..baa96d7 100644
--- a/protocol/river-window-management-v1.xml
+++ b/protocol/river-window-management-v1.xml
@@ -211,8 +211,8 @@
 
     <event name="render_start">
       <description summary="start a render sequence">
-        This event indicates that the server has sent all river_node_v1.position
-        and river_window_v1.dimensions events necessary.
+        This event indicates that the server has sent all
+        river_window_v1.dimensions events necessary.
 
         In response to this event, the client should make requests modifying
         rendering state as it chooses. Then, the client must make the
@@ -816,7 +816,7 @@
         maximized.
 
         The window manager is free to honor this request using
-        river_window_v1.inform_maximize or ignore it.
+        river_window_v1.inform_maximized or ignore it.
 
         This event will be followed by a manage_start event after all other new
         state has been sent by the server.
@@ -1358,7 +1358,7 @@
         mapping between wl_output and river_output_v1 objects.
 
         The global_remove event for the corresponding wl_output may be sent
-        before the river_output_v1.remove event. This is due to the fact that
+        before the river_output_v1.removed event. This is due to the fact that
         river_output_v1 state changes are synced to the river window management
         manage sequence while changes to globals are not.
 
@@ -1502,7 +1502,7 @@
         mapping between wl_seat and river_seat_v1 objects.
 
         The global_remove event for the corresponding wl_seat may be sent before
-        the river_seat_v1.remove event. This is due to the fact that
+        the river_seat_v1.removed event. This is due to the fact that
         river_seat_v1 state changes are synced to the river window management
         manage sequence while changes to globals are not.