diff options
| author | Diego Viola <diego.viola@gmail.com> | 2026-03-03 03:55:20 -0300 |
|---|---|---|
| committer | Diego Viola <diego.viola@gmail.com> | 2026-03-03 08:17:13 -0300 |
| commit | df10ef181e90ba8d0ce86e5f5e7280dad5d894c7 (patch) | |
| tree | 53db6e85ca40199ebe9db3e00841b41649a595a4 | |
| parent | util: assert alloc is consistent with data in wl_array_add() (diff) | |
| download | wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar.gz wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar.bz2 wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar.lz wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar.xz wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.tar.zst wayland-df10ef181e90ba8d0ce86e5f5e7280dad5d894c7.zip | |
Fix typos
Signed-off-by: Diego Viola <diego.viola@gmail.com>
| -rw-r--r-- | doc/book/src/Compositors.md | 2 | ||||
| -rw-r--r-- | doc/publican/Client.xml | 2 | ||||
| -rw-r--r-- | tests/data/bad-identifier-protocol.xml | 2 | ||||
| -rw-r--r-- | tests/test-compositor.c | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/book/src/Compositors.md b/doc/book/src/Compositors.md index 251be31..61d1bdb 100644 --- a/doc/book/src/Compositors.md +++ b/doc/book/src/Compositors.md @@ -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 application will then pass the Wayland server socket name to the embedded 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 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 diff --git a/doc/publican/Client.xml b/doc/publican/Client.xml index 19bf3e9..cb21598 100644 --- a/doc/publican/Client.xml +++ b/doc/publican/Client.xml @@ -25,7 +25,7 @@ are received from the server until they can be processed. Multi-threading is supported by creating an additional 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 object created. </para> diff --git a/tests/data/bad-identifier-protocol.xml b/tests/data/bad-identifier-protocol.xml index 7a17204..1aafb32 100644 --- a/tests/data/bad-identifier-protocol.xml +++ b/tests/data/bad-identifier-protocol.xml @@ -3,6 +3,6 @@ <interface name="required_interface" version="13"> <description summary="required summary"> </description> - <event name="requied_event"/> + <event name="required_event"/> </interface> </protocol> diff --git a/tests/test-compositor.c b/tests/test-compositor.c index efec31f..f412fe6 100644 --- a/tests/test-compositor.c +++ b/tests/test-compositor.c @@ -517,7 +517,7 @@ struct client *client_connect(void) assert(c->wl_display && "Failed connecting to display"); /* 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); assert(reg); wl_registry_add_listener(reg, ®istry_listener, c); |
