4 files changed, 5 insertions, 5 deletions
diff --git a/include/ruby/internal/encoding/string.h b/include/ruby/internal/encoding/string.h
index f8ce809199..6ed7ca1c90 100644
--- a/include/ruby/internal/encoding/string.h
+++ b/include/ruby/internal/encoding/string.h
@@ -190,7 +190,7 @@ VALUE rb_enc_str_buf_cat(VALUE str, const char *ptr, long len, rb_encoding *enc)
  * In  other languages,  APIs like  this  one could  be seen  as the  primitive
  * routines where encodings' "encode" feature are implemented.  However in case
  * of  Ruby this  is not  the primitive  one.  We  directly manipulate  encoded
- * strings.  Encoding conversion routines  transocde an encoded string directly
+ * strings.  Encoding conversion routines  transcode an encoded string directly
  * to another one; not via a code point array.
  */
 VALUE rb_enc_uint_chr(unsigned int code, rb_encoding *enc);
diff --git a/include/ruby/internal/fl_type.h b/include/ruby/internal/fl_type.h
index 47f054256b..08405d6f30 100644
--- a/include/ruby/internal/fl_type.h
+++ b/include/ruby/internal/fl_type.h
@@ -183,7 +183,7 @@ RB_GNUC_EXTENSION
  * @note  About the `FL_USER` terminology: the "user" here does not necessarily
  *        mean only  you.  For  instance struct  ::RString instances  use these
  *        bits to cache their encodings  etc.  Devs discussed about this topic,
- *        reached their  concensus that  ::RUBY_T_DATA is  the only  valid data
+ *        reached their  consensus that  ::RUBY_T_DATA is  the only  valid data
  *        structure that  can use these  bits; other data  structures including
  *        ::RUBY_T_OBJECT  use these  bits  for their  own  purpose.  See  also
  *        https://bugs.ruby-lang.org/issues/18059
diff --git a/include/ruby/internal/intern/gc.h b/include/ruby/internal/intern/gc.h
index 1617a7cef6..d8e476b078 100644
--- a/include/ruby/internal/intern/gc.h
+++ b/include/ruby/internal/intern/gc.h
@@ -249,7 +249,7 @@ void rb_gc(void);
  *
  * @internal
  *
- * But isn't it  easier for you to call super,  and let `Object#intialize_copy`
+ * But isn't it  easier for you to call super,  and let `Object#initialize_copy`
  * call this function instead?
  */
 void rb_gc_copy_finalizer(VALUE dst, VALUE src);
diff --git a/include/ruby/internal/intern/thread.h b/include/ruby/internal/intern/thread.h
index 294e552fe9..716375acd7 100644
--- a/include/ruby/internal/intern/thread.h
+++ b/include/ruby/internal/intern/thread.h
@@ -46,7 +46,7 @@ void rb_thread_schedule(void);
  *
  * @param[in]  fd                    A file descriptor.
  * @exception  rb_eIOError           Closed stream.
- * @exception  rb_eSystemCalleError  Situations like EBADF.
+ * @exception  rb_eSystemCallError   Situations like EBADF.
  */
 int rb_thread_wait_fd(int fd);
 
@@ -56,7 +56,7 @@ int rb_thread_wait_fd(int fd);
  *
  * @param[in]  fd                    A file descriptor.
  * @exception  rb_eIOError           Closed stream.
- * @exception  rb_eSystemCalleError  Situations like EBADF.
+ * @exception  rb_eSystemCallError   Situations like EBADF.
  */
 int rb_thread_fd_writable(int fd);