diff --git a/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml b/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
index d68ce0e..e94601c 100644
--- a/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
+++ b/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
@@ -95,32 +95,15 @@
ideally be sent before the first wl_surface.commit that maps the window.
Compositors are unlikely to substantially alter placement based on
suggestions sent after the window is already mapped and positioned.
+
+ This request causes the compositor to send the placement state, including
+ the output and logical coordinates where the toplevel is currently placed.
-
-
- This event notifies the client of the output and logical position where
- the compositor has actually placed the window, typically sent during
- the initial configuration sequence after considering any placement
- suggestions.
-
- This allows the client to know the result of its suggestion and update
- its stored state accurately. Compositors are not required to send this
- event if no suggestion was made or considered relevant to the final
- placement decision.
-
- Standard xdg_toplevel.configure events remain the primary source for
- ongoing size, state, and potentially position updates.
-
-
-
-
-
-
Requests the compositor to send the current placement state, including
@@ -130,9 +113,18 @@
- This event provides the current output and logical position where
- the compositor has placed the window. It is sent in response to a
- `get_placement_state` request.
+ This event notifies the client of the output and logical position where
+ the compositor has actually placed the window, typically sent during
+ the initial configuration sequence after considering any placement
+ suggestions, and in response to a `get_placement_state` request.
+
+ This allows the client to know the result of its suggestion and update
+ its stored state accurately. Compositors are not required to send this
+ event if no suggestion was made or considered relevant to the final
+ placement decision.
+
+ Standard xdg_toplevel.configure events remain the primary source for
+ ongoing size, state, and potentially position updates.