protocol: minor clarifications

This text was written prior to changes in the protocol that got rid of
the position event.

 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 15f7e12..e419651 100644
--- a/protocol/river-window-management-v1.xml
+++ b/protocol/river-window-management-v1.xml
@@ -82,10 +82,10 @@
 
       The server will start a render sequence by sending new state and the
       render_start event as soon as possible whenever there is a change in
-      window dimensions or position that must be communicated with the window
-      manager. Multiple render sequences may be made consecutively without a
-      manage sequence in between, for example during interactive move/resize of
-      windows or if a window independently changes its own dimensions.
+      window dimensions that must be communicated with the window manager.
+      Multiple render sequences may be made consecutively without a manage
+      sequence in between, for example if a window independently changes its own
+      dimensions.
 
       To summarize, the main loop of this protocol is as follows:
 
@@ -104,7 +104,7 @@
       5. The client sends requests modifying rendering state (as defined above)
          followed by the render_finish request.
 
-      6. If window dimensions/positions change, loop back to step 4.
+      6. If window dimensions change, loop back to step 4.
          If state that requires a manage sequence changes or if the client makes
          a manage_dirty request, loop back to step 1.