@@ -886,7 +886,7 @@ Argument Clinic generates code that does it for you (in the parsing function).
886886Advanced converters
887887-------------------
888888
889- Remeber those format units you skipped for your first
889+ Remember those format units you skipped for your first
890890time because they were advanced? Here's how to handle those too.
891891
892892The trick is, all those format units take arguments--either
@@ -1020,12 +1020,12 @@ any of the default arguments you can omit the parentheses.
10201020the ``"as" `` should come before the return converter.)
10211021
10221022There's one additional complication when using return converters: how do you
1023- indicate an error has occured ? Normally, a function returns a valid (non-``NULL ``)
1023+ indicate an error has occurred ? Normally, a function returns a valid (non-``NULL ``)
10241024pointer for success, and ``NULL `` for failure. But if you use an integer return converter,
10251025all integers are valid. How can Argument Clinic detect an error? Its solution: each return
10261026converter implicitly looks for a special value that indicates an error. If you return
10271027that value, and an error has been set (``PyErr_Occurred() `` returns a true
1028- value), then the generated code will propogate the error. Otherwise it will
1028+ value), then the generated code will propagate the error. Otherwise it will
10291029encode the value you return like normal.
10301030
10311031Currently Argument Clinic supports only a few return converters::
@@ -1573,7 +1573,7 @@ The fourth new directive is ``set``::
15731573``line_prefix `` is a string that will be prepended to every line of Clinic's output;
15741574``line_suffix `` is a string that will be appended to every line of Clinic's output.
15751575
1576- Both of these suport two format strings:
1576+ Both of these support two format strings:
15771577
15781578 ``{block comment start} ``
15791579 Turns into the string ``/* ``, the start-comment text sequence for C files.
0 commit comments