Skip to content

Commit 55a6102

Browse files
WolframAlphsrinivasreddy
authored andcommitted
pythongh-119786: Fix typos in InternalDocs/frames.md (python#128275)
Fix typos in `InternalDocs/frames.md`
1 parent dc60148 commit 55a6102

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Diff for: InternalDocs/frames.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Each activation record is laid out as:
3333
* Stack
3434

3535
This seems to provide the best performance without excessive complexity.
36-
The specials have a fixed size, so the offset of the locals is know. The
36+
The specials have a fixed size, so the offset of the locals is known. The
3737
interpreter needs to hold two pointers, a frame pointer and a stack pointer.
3838

3939
#### Alternative layout
@@ -52,7 +52,7 @@ an extra pointer for the locals, which can hurt performance.
5252
### Generators and Coroutines
5353

5454
Generators and coroutines contain a `_PyInterpreterFrame`
55-
The specials sections contains the following pointers:
55+
The specials section contains the following pointers:
5656

5757
* Globals dict
5858
* Builtins dict
@@ -69,7 +69,7 @@ and builtins, than strong references to both globals and builtins.
6969

7070
When creating a backtrace or when calling `sys._getframe()` the frame becomes
7171
visible to Python code. When this happens a new `PyFrameObject` is created
72-
and a strong reference to it placed in the `frame_obj` field of the specials
72+
and a strong reference to it is placed in the `frame_obj` field of the specials
7373
section. The `frame_obj` field is initially `NULL`.
7474

7575
The `PyFrameObject` may outlive a stack-allocated `_PyInterpreterFrame`.
@@ -128,7 +128,7 @@ The `return_offset` field determines where a `RETURN` should go in the caller,
128128
relative to `instr_ptr`. It is only meaningful to the callee, so it needs to
129129
be set in any instruction that implements a call (to a Python function),
130130
including CALL, SEND and BINARY_SUBSCR_GETITEM, among others. If there is no
131-
callee, then return_offset is meaningless. It is necessary to have a separate
131+
callee, then return_offset is meaningless. It is necessary to have a separate
132132
field for the return offset because (1) if we apply this offset to `instr_ptr`
133133
while executing the `RETURN`, this is too early and would lose us information
134134
about the previous instruction which we could need for introspecting and

0 commit comments

Comments
 (0)