diff --git a/NEWS.md b/NEWS.md
index f6dc9263d00b64..17dfca8d1c6b86 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -307,7 +307,7 @@ changelog for details of the default gems or bundled gems.
     * added: `rb_postponed_job_preregister()`
     * added: `rb_postponed_job_trigger()`
     * deprecated: `rb_postponed_job_register()` (and semantic change. see below)
-    * deprecated: `rb_postponed_job_register_once()`
+    * deprecated: `rb_postponed_job_register_one()`
   * The postponed job APIs have been changed to address some rare crashes.
     To solve the issue, we introduced new two APIs and deprecated current APIs.
     The semantics of these functions have also changed slightly; `rb_postponed_job_register`
diff --git a/include/ruby/debug.h b/include/ruby/debug.h
index 9861c96cd87961..6202ce1c72bb0a 100644
--- a/include/ruby/debug.h
+++ b/include/ruby/debug.h
@@ -643,11 +643,11 @@ VALUE rb_tracearg_object(rb_trace_arg_t *trace_arg);
  * racing with Ruby's internal use of them. These two functions are still present,
  * but are marked as deprecated and have slightly changed semantics:
  *
- * * rb_postponed_job_register now works like rb_postponed_job_register_once i.e.
+ * * rb_postponed_job_register now works like rb_postponed_job_register_one i.e.
  *   `func` will only be executed at most one time each time Ruby checks for
  *   interrupts, no matter how many times it is registered
  * * They are also called with the last `data` to be registered, not the first
- *   (which is how rb_postponed_job_register_once previously worked)
+ *   (which is how rb_postponed_job_register_one previously worked)
  */