Spelling fixes

7 files changed, 9 insertions, 9 deletions

diff --git a/src/androidselect.c b/src/androidselect.c
index 50982738743..d5783b75417 100644
--- a/src/androidselect.c
+++ b/src/androidselect.c
@@ -945,7 +945,7 @@ keywords is understood:
                 No more than three actions defined here will be
                 displayed, not counting any with "default" as its
                 key.
-  :timeout      Number of miliseconds from the display of the
+  :timeout      Number of milliseconds from the display of the
                 notification at which it will be automatically
                 dismissed, or a value of zero or smaller if it
                 is to remain until user action is taken to dismiss
diff --git a/src/fns.c b/src/fns.c
index 48607b2c5d0..371d2ae3a3a 100644
--- a/src/fns.c
+++ b/src/fns.c
@@ -5359,7 +5359,7 @@ hash_string (char const *ptr, ptrdiff_t len)
           hash = sxhash_combine (hash, c);
         }
       while (p + sizeof hash <= end);
-      /* Hash the last wordful of bytes in the string, because that is
+      /* Hash the last word's worth of bytes in the string, because that is
          is often the part where strings differ.  This may cause some
          bytes to be hashed twice but we assume that's not a big problem.  */
       EMACS_UINT c;
diff --git a/src/itree.c b/src/itree.c
index da51b3c61fd..9dae279db90 100644
--- a/src/itree.c
+++ b/src/itree.c
@@ -1211,7 +1211,7 @@ itree_node_intersects (const struct itree_node *node,
    `ITER->begin..ITER->end`) so it will also return some nodes which aren't in
    that narrowing simply because they may have children which are.
 
-   The code itself is very unsatifactory because the code of each one
+   The code itself is very unsatisfactory because the code of each one
    of the supported traversals seems completely different from the others.
    If someone knows how to make it more uniform and "obviously correct",
    please make yourself heard.  */
diff --git a/src/json.c b/src/json.c
index 140c3625d4d..21066d21328 100644
--- a/src/json.c
+++ b/src/json.c
@@ -405,7 +405,7 @@ json_out_nest (json_out_t *jo)
 {
   --jo->maxdepth;
   if (jo->maxdepth < 0)
-    error ("Maximum JSON serialisation depth exceeded");
+    error ("Maximum JSON serialization depth exceeded");
 }
 
 static void
diff --git a/src/macros.c b/src/macros.c
index 230195d9488..a4df125aafd 100644
--- a/src/macros.c
+++ b/src/macros.c
@@ -343,14 +343,14 @@ buffer before the macro is executed.  */)
      restore Vexecuting_kbd_macro and executing_kbd_macro_index, and
      run 'kbd-macro-termination-hook'.
 
-     If read_char happens to be called at the end of a macro interation,
+     If read_char happens to be called at the end of a macro iteration,
      but before read_key_sequence could handle the end (e.g., when lisp
      code calls 'read-event', 'read-char', or 'read-char-exclusive'),
      read_char will simply continue reading other available input
      (Bug#68272).  Vexecuting_kbd_macro and executing_kbd_macro remain
      untouched until the end of the iteration is handled.
 
-     This is similar (in observable behavior) to a posibly simpler
+     This is similar (in observable behavior) to a possibly simpler
      implementation of keyboard macros in which this function pushed all
      characters of the macro into the incoming event queue and returned
      immediately.  Maybe this is the implementation that we ideally
diff --git a/src/sort.c b/src/sort.c
index dc9f49016aa..24c3e94f50c 100644
--- a/src/sort.c
+++ b/src/sort.c
@@ -1130,7 +1130,7 @@ tim_sort (Lisp_Object predicate, Lisp_Object keyfunc,
       keys[i] = call1 (keyfunc, seq[i]);
 
   /* FIXME: This is where we would check the keys for interesting
-     properties for more optimised comparison (such as all being fixnums
+     properties for more optimized comparison (such as all being fixnums
      etc).  */
 
   /* March over the array once, left to right, finding natural runs,
diff --git a/src/xdisp.c b/src/xdisp.c
index 3d8651f4086..4df76baf92b 100644
--- a/src/xdisp.c
+++ b/src/xdisp.c
@@ -19173,7 +19173,7 @@ try_scrolling (Lisp_Object window, bool just_this_one_p,
       /* Maybe forget recorded base line for line number display.  */
       /* FIXME: Why do we need this?  `try_scrolling` can only be called from
          `redisplay_window` which should have flushed this cache already when
-         eeded.  */
+         needed.  */
       if (!BASE_LINE_NUMBER_VALID_P (w))
         w->base_line_number = 0;
 
@@ -35810,7 +35810,7 @@ note_fringe_highlight (struct frame *f, Lisp_Object window, int x, int y,
 
   /* NOTE: iterating over glyphs can only find text properties coming
      from visible text.  This means that zero-length overlays and
-     invisibile text are NOT inspected.  */
+     invisible text are NOT inspected.  */
   for (; glyph_num; glyph_num--, glyph++)
     {
       Lisp_Object pos = make_fixnum (glyph->charpos);