src: use transferred consistently

This commit updates usages of transfered to be transferred to make it
consist in all comments.

PR-URL: https://github.com/nodejs/node/pull/36340
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Yuta Hiroto <hello@hiroppy.me>

1 files changed, 4 insertions, 4 deletions

diff --git a/src/base_object.h b/src/base_object.h
index 54ebeb52041..3eac795e783 100644
--- a/src/base_object.h
+++ b/src/base_object.h
@@ -116,13 +116,13 @@ class BaseObject : public MemoryRetainer {
   // the current object:
   // - kUntransferable:
   //     No transfer is possible, either because this type of BaseObject does
-  //     not know how to be transfered, or because it is not in a state in
+  //     not know how to be transferred, or because it is not in a state in
   //     which it is possible to do so (e.g. because it has already been
-  //     transfered).
+  //     transferred).
   // - kTransferable:
-  //     This object can be transfered in a destructive fashion, i.e. will be
+  //     This object can be transferred in a destructive fashion, i.e. will be
   //     rendered unusable on the sending side of the channel in the process
-  //     of being transfered. (In C++ this would be referred to as movable but
+  //     of being transferred. (In C++ this would be referred to as movable but
   //     not copyable.) Objects of this type need to be listed in the
   //     `transferList` argument of the relevant postMessage() call in order to
   //     make sure that they are not accidentally destroyed on the sending side.