summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDiego Viola <diego.viola@gmail.com>2012-05-23 02:08:08 -0400
committerKristian Høgsberg <krh@bitplanet.net>2012-05-23 09:10:00 -0400
commit00de1e6cce5f3389eb763d80df7135f19ccda1be (patch)
tree40741a1d38dcf1621e55aaecd9daecabbc610c0f
parent5030af7635fc24b325a22d823ab0f51a4b099762 (diff)
fix typo
-rw-r--r--README2
-rw-r--r--TODO4
2 files changed, 3 insertions, 3 deletions
diff --git a/README b/README
index b8ad9b4..64904ed 100644
--- a/README
+++ b/README
@@ -12,7 +12,7 @@ buffer management. The compositor receives input events and forwards
them to the relevant client. The clients creates buffers and renders
into them and notifies the compositor when it needs to redraw. The
protocol also handles drag and drop, selections, window management and
-other interactions that must go throught the compositor. However, the
+other interactions that must go through the compositor. However, the
protocol does not handle rendering, which is one of the features that
makes wayland so simple. All clients are expected to handle rendering
themselves, typically through cairo or OpenGL.
diff --git a/TODO b/TODO
index c8dcbac..abdab31 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,8 @@
Core wayland protocol
- We need rotation information in the output (multiples of 90
- degress) and we'll need a way for a client to communicate that it
- has rendered it's buffer according to the output rotation. The
+ degrees) and we'll need a way for a client to communicate that it
+ has rendered its buffer according to the output rotation. The
goal is to be able to pageflip directly to the client buffer, and
for that we need the client to render accordingly and the
compositor needs to know that it did.