diff --git a/NOTES b/NOTES
index 24b30178..0fa279bd 100644
--- a/NOTES
+++ b/NOTES
@@ -1,7 +1,7 @@
 Comments on various aspects of KRfb:
 
 - KRfb has been designed for three use cases:
-  * a user who needs help from an administrator or friend. The adminstrator can 
+  * a user who needs help from an administrator or friend. The administrator can 
     connect to the user and change settings and so on while both are talking
     on the telephone or using VoIP.
   * a user who wants to show something to a friend, so he lets his friend
@@ -12,7 +12,7 @@ Comments on various aspects of KRfb:
   so KRfb is pre-configured for them. Case 3 is for advanced users and
   therefore a little bit more difficult to configure.
 - design goal of KRfb is to make it as easy to use as possible. I tried to
-  limit functionality whereever possible.
+  limit functionality wherever possible.
 - the new-connection-dialog is extra large and has the pixmap on the left
   side to capture the attention of the user before allowing a connection.
 - the RFBController class is a mess. The interactions between the threaded, 
diff --git a/framebuffers/xcb/xcb_framebuffer.cpp b/framebuffers/xcb/xcb_framebuffer.cpp
index 7f015b5d..504d9ac6 100644
--- a/framebuffers/xcb/xcb_framebuffer.cpp
+++ b/framebuffers/xcb/xcb_framebuffer.cpp
@@ -551,7 +551,7 @@ QList<QRect> XCBFrameBuffer::modifiedTiles() {
                 // get image data into shared memory segment
                 // now rects are positioned relative to framebufferImage,
                 // but we need to get image from the whole screen, so
-                // translate whe coordinates
+                // translate the coordinates
                 xcb_shm_get_image_cookie_t sgi_cookie = xcb_shm_get_image(
                             QX11Info::connection(),
                             d->win,