CodeSpell

wayland-protocols/wayland.xml

@@ -1511,7 +1511,7 @@
 
 	Destroying the wl_buffer after wl_buffer.release does not change
 	the surface contents. Destroying the wl_buffer before wl_buffer.release
-	is allowed as long as the underlying buffer storage isn't re-used (this
+	is allowed as long as the underlying buffer storage isn't reused (this
 	can happen e.g. on client process termination). However, if the client
 	destroys the wl_buffer before receiving the wl_buffer.release event and
 	mutates the underlying buffer storage, the surface contents become
@@ -2003,8 +2003,8 @@
 	before announcing capabilities. This event only sent once per seat object,
 	and the name does not change over the lifetime of the wl_seat global.
 
-	Compositors may re-use the same seat name if the wl_seat global is
-	destroyed and re-created later.
+	Compositors may reuse the same seat name if the wl_seat global is
+	destroyed and recreated later.
       </description>
       <arg name="name" type="string" summary="seat identifier"/>
     </event>
@@ -2972,8 +2972,8 @@
 	only sent once per output object, and the name does not change over the
 	lifetime of the wl_output global.
 
-	Compositors may re-use the same output name if the wl_output global is
-	destroyed and re-created later. Compositors should avoid re-using the
+	Compositors may reuse the same output name if the wl_output global is
+	destroyed and recreated later. Compositors should avoid reusing the
 	same name if possible.
 
 	The name event will be followed by a done event.
@@ -3288,7 +3288,7 @@
 
 	The compositor will emit a wl_display.delete_id event with the object ID
 	of the registry and will no longer emit any events on the registry. The
-	client should re-use the object ID once it receives the
+	client should reuse the object ID once it receives the
 	wl_display.delete_id event.
       </description>
       <arg name="registry" type="object" interface="wl_registry"