diff --git a/doc/publican/sources/Architecture.xml b/doc/publican/sources/Architecture.xml
index 5d9ada0..b8a104c 100644
--- a/doc/publican/sources/Architecture.xml
+++ b/doc/publican/sources/Architecture.xml
@@ -114,7 +114,7 @@
       As suggested above, there are a few problems with this
       approach. The X server doesn't have the information to
       decide which window should receive the event, nor can it
-      transform the screen coordinates to window local
+      transform the screen coordinates to window-local
       coordinates. And even though X has handed responsibility for
       the final painting of the screen to the compositing manager,
       X still controls the front buffer and modesetting. Most of
@@ -172,7 +172,7 @@
 	    in the scenegraph. Thus, the
 	    compositor can pick the right window
 	    and transform the screen coordinates
-	    to window local coordinates, by
+	    to window-local coordinates, by
 	    applying the inverse
 	    transformations. The types of
 	    transformation that can be applied
diff --git a/doc/publican/sources/Protocol.xml b/doc/publican/sources/Protocol.xml
index 66cebfb..481e175 100644
--- a/doc/publican/sources/Protocol.xml
+++ b/doc/publican/sources/Protocol.xml
@@ -333,7 +333,7 @@
       A seat represents a group of input devices including mice,
       keyboards and touchscreens. It has a keyboard and pointer
       focus. Seats are global objects. Pointer events are delivered
-      in surface local coordinates.
+      in surface-local coordinates.
     </para>
     <para>
       The compositor maintains an implicit grab when a button is