Skip to content

Commit 05c1b38

Browse files
bombs-kimmiss-islington
authored andcommitted
Fixed a few obvious mistakes in c-api docs (GH-11184)
I thought these simple changes doesn't need bpo number(Am I right..?). Please refer to the commit message for detail.
1 parent 3ab064e commit 05c1b38

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Doc/c-api/intro.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,7 @@ duration of the call.
234234
However, a common pitfall is to extract an object from a list and hold on to it
235235
for a while without incrementing its reference count. Some other operation might
236236
conceivably remove the object from the list, decrementing its reference count
237-
and possible deallocating it. The real danger is that innocent-looking
237+
and possibly deallocating it. The real danger is that innocent-looking
238238
operations may invoke arbitrary Python code which could do this; there is a code
239239
path which allows control to flow back to the user from a :c:func:`Py_DECREF`, so
240240
almost any operation is potentially dangerous.

Doc/c-api/refcounting.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ objects.
5858
the macro carefully uses a temporary variable and sets the argument to *NULL*
5959
before decrementing its reference count.
6060
61-
It is a good idea to use this macro whenever decrementing the value of a
62-
variable that might be traversed during garbage collection.
61+
It is a good idea to use this macro whenever decrementing the reference
62+
count of an object that might be traversed during garbage collection.
6363
6464
6565
The following functions are for runtime dynamic embedding of Python:

0 commit comments

Comments
 (0)