summaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorLiu, Xinyun <xinyunliu@gmail.com>2011-02-18 13:40:49 (GMT)
committerKristian Høgsberg <krh@bitplanet.net>2011-02-18 13:40:49 (GMT)
commit9a2015562c29ddbb34a8b9d2e001ec12a660c28d (patch)
treeb1f863c1128f9a609edec905fe7c590bc51ce20d /spec
parentfcfb4e30a47a4cd2416dac210521594b489c8bfd (diff)
downloadwayland-9a2015562c29ddbb34a8b9d2e001ec12a660c28d.tar.gz
wayland-9a2015562c29ddbb34a8b9d2e001ec12a660c28d.tar.xz
Several typo fixes in specs/main.tex
Diffstat (limited to 'spec')
-rw-r--r--spec/main.tex10
1 files changed, 5 insertions, 5 deletions
diff --git a/spec/main.tex b/spec/main.tex
index 1b17557..f32e999 100644
--- a/spec/main.tex
+++ b/spec/main.tex
@@ -64,7 +64,7 @@ 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 response to a request
(in which case the request and the event constitutes a round trip) or
-spontanously when the server state changes.
+spontaneously when the server state changes.
\begin{itemize}
\item state is broadcast on connect, events sent out when state
@@ -83,8 +83,8 @@ clients and compositors.
The protocol entry points are generated as inline functions which just
wraps the \verb:wl_proxy_*: functions. The inline functions aren't
-part of the library ABI and languange bindings should generate their
-own stubs for the protocl entry points from the xml.
+part of the library ABI and language bindings should generate their
+own stubs for the protocol entry points from the xml.
\subsection{Wire format}
@@ -222,7 +222,7 @@ Talk about:
A surface can change the pointer image when the surface is the pointer
focus of the input device. Wayland doesn't automatically change the
pointer image when a pointer enters a surface, but expects the
-application to set the cursor it wants in response the the pointer
+application to set the cursor it wants in response the pointer
focus and motion events. The rationale is that a client has to manage
changing pointer images for UI elements within the surface in response
to motion events anyway, so we'll make that the only mechanism for
@@ -326,7 +326,7 @@ Issues:
\item Should drag.send() destroy the object? There's nothing to do
after the data has been transferred.
-\item How do we marshall several mime-types? We could make the drag
+\item How do we marshal several mime-types? We could make the drag
setup a multi-step operation: dnd.create, drag.offer(mime-type1),
drag.offer(mime-type2), drag.activate(). The drag object could send
multiple offer events on each motion event. Or we could just