Skip to content

Commit 7af4b9f

Browse files
authored
Docs: fix spelling of the word 'transferring' (#116641)
1 parent cef0ec1 commit 7af4b9f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Python/tier2_engine.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ The JIT compiler converts superblocks into machine code executors.
5252
These have identical behavior to interpreted executors, except that
5353
they consume more memory for the generated machine code and are a lot faster.
5454

55-
## Transfering control
55+
## Transferring control
5656

5757
There are three types of control transfer that we need to consider:
5858
* Tier 1 to tier 2
@@ -104,7 +104,7 @@ reference to the previous executor in the thread state's
104104
#### The interpreter
105105

106106
The tier 2 interpreter has a variable `current_executor` which
107-
points to the currently live executor. When transfering from executor
107+
points to the currently live executor. When transferring from executor
108108
`A` to executor `B` we do the following:
109109
(Initially `current_executor` points to `A`, and the refcount of
110110
`A` is elevated by one)
@@ -122,7 +122,7 @@ increment the refcount of `B` and set `current_executor` to point to `B`.
122122

123123
#### In the JIT
124124

125-
Transfering control from one executor to another is done via tailcalls.
125+
Transferring control from one executor to another is done via tailcalls.
126126

127127
The compiled executor should do the same, except that there is no local
128128
variable `current_executor`.

0 commit comments

Comments
 (0)