mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2026-03-16 05:34:32 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typos

Browse source 
Signed-off-by: Diego Viola <diego.viola@gmail.com>
This commit is contained in:
Diego Viola 2026-03-03 03:55:20 -03:00
parent fe3a02c18a
commit df10ef181e
4 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/book/src/Compositors.md
View file

@ -66,7 +66,7 @@ Another option is to use a nested Wayland instance. For this, the Wayland server
will have to be a library that the host application links to. The host will have to be a library that the host application links to. The host
application will then pass the Wayland server socket name to the embedded application will then pass the Wayland server socket name to the embedded
application, and will need to implement the Wayland compositor interface. The application, and will need to implement the Wayland compositor interface. The
host application composites the client surfaces as part of it's window, that is, host application composites the client surfaces as part of its window, that is,
in the web page or in the panel. The benefit of nesting the Wayland server is in the web page or in the panel. The benefit of nesting the Wayland server is
that it provides the requests the embedded client needs to inform the host about that it provides the requests the embedded client needs to inform the host about
buffer updates and a mechanism for forwarding input events from the host buffer updates and a mechanism for forwarding input events from the host

2
doc/publican/Client.xml
View file

@ -25,7 +25,7 @@
are received from the server until they can be are received from the server until they can be
processed. Multi-threading is supported by creating an additional processed. Multi-threading is supported by creating an additional
wl_event_queue for each additional thread, each object can have wl_event_queue for each additional thread, each object can have
it's events placed in a particular queue, so potentially a its events placed in a particular queue, so potentially a
different thread could be made to handle the events for each different thread could be made to handle the events for each
object created. object created.
</para> </para>

2
tests/data/bad-identifier-protocol.xml
View file

@ -3,6 +3,6 @@
<interface name="required_interface" version="13"> <interface name="required_interface" version="13">
<description summary="required summary"> <description summary="required summary">
</description> </description>
<event name="requied_event"/> <event name="required_event"/>
</interface> </interface>
</protocol> </protocol>

2
tests/test-compositor.c
View file

@ -517,7 +517,7 @@ struct client *client_connect(void)
assert(c->wl_display && "Failed connecting to display"); assert(c->wl_display && "Failed connecting to display");
/* create test_compositor proxy. Do it with temporary /* create test_compositor proxy. Do it with temporary
* registry so that client can define it's own listener later */ * registry so that client can define its own listener later */
reg = wl_display_get_registry(c->wl_display); reg = wl_display_get_registry(c->wl_display);
assert(reg); assert(reg);
wl_registry_add_listener(reg, &registry_listener, c); wl_registry_add_listener(reg, &registry_listener, c);