diff --git a/doc/scripts/gdb/flight_rec.py b/doc/scripts/gdb/flight_rec.py
index 9872f17f..66ff25f0 100755
--- a/doc/scripts/gdb/flight_rec.py
+++ b/doc/scripts/gdb/flight_rec.py
@@ -52,7 +52,7 @@ class DisplayFlightRecorder(gdb.Command):
         # display this data (only) if symbol is not empty (happens if the program is not ran at all)
         if rb.value():
             print("Data at byte {append}, Size: {size}B, "
-                  "Overlaped: {overlap}".format(append=rb.value()['append_pos'],
+                  "Overlapped: {overlap}".format(append=rb.value()['append_pos'],
                                                 size=rb.value()['size'],
                                                 overlap=rb.value()['overlap']))
 
diff --git a/doc/sphinx/toc/libweston/log.rst b/doc/sphinx/toc/libweston/log.rst
index d768de0d..34e92543 100644
--- a/doc/sphinx/toc/libweston/log.rst
+++ b/doc/sphinx/toc/libweston/log.rst
@@ -109,7 +109,7 @@ initial/original one.
 
 .. note::
 
-   The subscription process is (an) internal API and is managed implictly.
+   The subscription process is (an) internal API and is managed implicitly.
 
 When a scope is being destroyed the subscriptions for this scope will be
 destroyed as well.
@@ -117,7 +117,7 @@ destroyed as well.
 Logger
 ~~~~~~
 
-weston uses a logger type of a subscriber for logging everyhing in the code
+weston uses a logger type of a subscriber for logging everything in the code
 (through the help of :func:`weston_log()`).  The subscriber method
 (:func:`weston_log_subscriber_create_log()`) takes an :samp:`FILE *` as an
 argument in case the std :samp:`stdout` file-descriptor is not where the data
diff --git a/doc/sphinx/toc/libweston/output.rst b/doc/sphinx/toc/libweston/output.rst
index 6bd4bf96..6ca69162 100644
--- a/doc/sphinx/toc/libweston/output.rst
+++ b/doc/sphinx/toc/libweston/output.rst
@@ -7,7 +7,7 @@ A :type:`weston_output` determines what part of the global compositor
 coordinate space will be composited into an image and when. That image is
 presented on the attached heads (weston_head).
 
-An output object is resposible for the framebuffer management, damage tracking,
+An output object is responsible for the framebuffer management, damage tracking,
 display timings, and the repaint state machine. Video mode, output scale and
 output transform are properties of an output.