And one in the main.tex spec document.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
its clients as well as a library implementation of the protocol. The
compositor can be a standalone display server running on Linux kernel
modesetting and evdev input devices, an X applications, or a wayland
its clients as well as a library implementation of the protocol. The
compositor can be a standalone display server running on Linux kernel
modesetting and evdev input devices, an X applications, or a wayland
-client itself. The clients can be traditional appliactions, X servers
+client itself. The clients can be traditional applications, X servers
(rootless or fullscreen) or other display servers.
The wayland protocol is essentially only about input handling and
(rootless or fullscreen) or other display servers.
The wayland protocol is essentially only about input handling and
Wayland needs libxkbcommon for translating evdev keycodes to keysyms.
There's a couple of repos around, and we're trying to consolidate the
Wayland needs libxkbcommon for translating evdev keycodes to keysyms.
There's a couple of repos around, and we're trying to consolidate the
-development, but for wayland you'll need the repo from my get
+development, but for wayland you'll need the repo from my git
repository. For this you'll need development packages for xproto,
kbproto and libX11.
repository. For this you'll need development packages for xproto,
kbproto and libX11.
-The Waland clients render using cairo-gl, which is an experimental
+The Wayland clients render using cairo-gl, which is an experimental
cairo backend. It has been available since cairo 1.10. Unless your
distribution ships cairo with the gl backend enabled, you'll need to
compile your own version of cairo:
cairo backend. It has been available since cairo 1.10. Unless your
distribution ships cairo with the gl backend enabled, you'll need to
compile your own version of cairo:
The server sends back events to the client, each event is emitted from
an object. Events can be error conditions. The event includes the
object id and the event opcode, from which the client can determine
The server sends back events to the client, each event is emitted from
an object. Events can be error conditions. The event includes the
object id and the event opcode, from which the client can determine
-the type of event. Events are generated both in repsonse to a request
+the type of event. Events are generated both in response to a request
(in which case the request and the event constitutes a round trip) or
spontanously when the server state changes.
(in which case the request and the event constitutes a round trip) or
spontanously when the server state changes.