mirror of
https://gitlab.freedesktop.org/wayland/wayland.git
synced 2026-03-07 04:34:49 -05:00
Fix typos
Signed-off-by: Diego Viola <diego.viola@gmail.com>
This commit is contained in:
parent
fe3a02c18a
commit
df10ef181e
4 changed files with 4 additions and 4 deletions
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue