Docs: Fix documentation typos in C files #125570
Conversation
That is, documentation only typos in .c and .h files.
ember91
requested review from
a team,
1st1,
berkerpeksag,
ericsnowcurrently,
erlend-aasland,
iritkatriel,
kumaraditya303,
lysnikolaou,
markshannon and
pablogsal
as code owners
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
| // Asserts that the mutex is locked. The mutex must be held by the | ||
| // top-most critical section otherwise there's the possibility | ||
| // that the mutex would be swalled out in some code paths. | ||
| // that the mutex would be stalled out in some code paths. |
There was a problem hiding this comment.
Not sure what swalled is supposed to mean. I can just revert this change and the same one below if you want.
There was a problem hiding this comment.
@DinoV wrote this.
Refuse the temptation to guess unless you know what it means.
Having said that, my best guess is “swapped out”. The LL and PP keys are in the same corner of my keyboard.
This comment was marked as outdated.
This comment was marked as outdated.
| /* There are two flavours of 'nice': one that returns the new | ||
| priority (as required by almost all standards out there) and the | ||
| Linux/FreeBSD one, which returns '0' on success and advices | ||
| Linux/FreeBSD one, which returns '0' on success and advises |
There was a problem hiding this comment.
Please revert. advices is perfectly legal.
There was a problem hiding this comment.
Advices seems to be plural of the noun while advises is the verb. I think this is right.
|
|
||
| /* | ||
| * Define the PyRecurdingInfinitelyError_Type | ||
| * Define the PyRecurringInfinitelyError_Type |
There was a problem hiding this comment.
| * Define the PyRecurringInfinitelyError_Type | |
| * Define the PyRecursingInfinitelyError type |
| // Asserts that the mutex is locked. The mutex must be held by the | ||
| // top-most critical section otherwise there's the possibility | ||
| // that the mutex would be swalled out in some code paths. | ||
| // that the mutex would be stalled out in some code paths. |
There was a problem hiding this comment.
@DinoV wrote this.
Refuse the temptation to guess unless you know what it means.
Having said that, my best guess is “swapped out”. The LL and PP keys are in the same corner of my keyboard.
|
Closing this PR. I will follow the suggestions by @willingc in #125569 (review), but also its follow up #125569 (comment). I will apply all suggestions in this PR this far in new PRs, obviously. |
4 participants
That is, documentation only typos in .c and .h files.
See #125473 for context.