summaryrefslogtreecommitdiff
path: root/src/x11
diff options
context:
space:
mode:
authorBjörn Daase <bjoern@daase.net>2020-08-26 11:49:50 +0200
committerRobert Mader <robert.mader@posteo.de>2020-08-29 09:10:31 +0000
commit5ec9bde64fbc07e057e78b04c3b0b66a86c07f6e (patch)
treebb6ff2135560a15d0bfaab7ddf07bef095a217ae /src/x11
parent5962ee79390a34e8b550bc6deb21b402182ca11e (diff)
downloadmutter-5ec9bde64fbc07e057e78b04c3b0b66a86c07f6e.tar.gz
*: Fix spelling mistakes found by codespell
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1410
Diffstat (limited to 'src/x11')
-rw-r--r--src/x11/events.c2
-rw-r--r--src/x11/meta-x11-display.c2
-rw-r--r--src/x11/window-x11.c2
3 files changed, 3 insertions, 3 deletions
diff --git a/src/x11/events.c b/src/x11/events.c
index 8ca2fb983..8c78b2ff1 100644
--- a/src/x11/events.c
+++ b/src/x11/events.c
@@ -1386,7 +1386,7 @@ handle_other_xevent (MetaX11Display *x11_display,
}
break;
case MapNotify:
- /* NB: override redirect windows wont cause a map request so we
+ /* NB: override redirect windows won't cause a map request so we
* watch out for map notifies against any root windows too if a
* compositor is enabled: */
if (window == NULL && event->xmap.event == x11_display->xroot)
diff --git a/src/x11/meta-x11-display.c b/src/x11/meta-x11-display.c
index 87d8a2bfa..525d0cab6 100644
--- a/src/x11/meta-x11-display.c
+++ b/src/x11/meta-x11-display.c
@@ -448,7 +448,7 @@ query_xi_extension (MetaX11Display *x11_display)
}
/*
- * Initialises the bell subsystem. This involves intialising
+ * Initialises the bell subsystem. This involves initialising
* XKB (which, despite being a keyboard extension, is the
* place to look for bell notifications), then asking it
* to send us bell notifications, and then also switching
diff --git a/src/x11/window-x11.c b/src/x11/window-x11.c
index ff8361540..ea9e82c8f 100644
--- a/src/x11/window-x11.c
+++ b/src/x11/window-x11.c
@@ -1505,7 +1505,7 @@ meta_window_x11_move_resize_internal (MetaWindow *window,
* we grow the frame more than we shrink. The idea is to avoid
* messing up the window contents by having a temporary situation
* where the frame is smaller than the window. However, if we're
- * cooperating with the client to create an atomic frame upate,
+ * cooperating with the client to create an atomic frame update,
* and the window is redirected, then we should always update
* the frame first, since updating the frame will force a new
* backing pixmap to be allocated, and the old backing pixmap