mirror of https://github.com/python/cpython
Docs: fix typos in documentation (#118752)
This commit is contained in:
parent
c68311df85
commit
7b0c247f1c
|
@ -41,7 +41,7 @@ The :class:`EmailMessage` dictionary-like interface is indexed by the header
|
|||
names, which must be ASCII values. The values of the dictionary are strings
|
||||
with some extra methods. Headers are stored and returned in case-preserving
|
||||
form, but field names are matched case-insensitively. The keys are ordered,
|
||||
but unlike a real dict, there can be duplicates. Addtional methods are
|
||||
but unlike a real dict, there can be duplicates. Additional methods are
|
||||
provided for working with headers that have duplicate keys.
|
||||
|
||||
The *payload* is either a string or bytes object, in the case of simple message
|
||||
|
|
|
@ -429,7 +429,7 @@ Several non-character keys move the cursor and possibly
|
|||
delete characters. Deletion does not puts text on the clipboard,
|
||||
but IDLE has an undo list. Wherever this doc discusses keys,
|
||||
'C' refers to the :kbd:`Control` key on Windows and
|
||||
Unix and the :kbd:`Command` key on macOS. (And all such dicussions
|
||||
Unix and the :kbd:`Command` key on macOS. (And all such discussions
|
||||
assume that the keys have not been re-bound to something else.)
|
||||
|
||||
* Arrow keys move the cursor one character or line.
|
||||
|
|
|
@ -210,7 +210,7 @@ XMLParser Objects
|
|||
by default until a sufficient amount of input is reached.
|
||||
Due to this delay, registered handlers may — depending of the sizing of
|
||||
input chunks pushed to Expat — no longer be called right after pushing new
|
||||
input to the parser. Where immediate feedback and taking over responsiblity
|
||||
input to the parser. Where immediate feedback and taking over responsibility
|
||||
of protecting against denial of service from large tokens are both wanted,
|
||||
calling ``SetReparseDeferralEnabled(False)`` disables reparse deferral
|
||||
for the current Expat parser instance, temporarily or altogether.
|
||||
|
|
|
@ -160,7 +160,7 @@ events, use the expression ``PY_RETURN | PY_START``.
|
|||
|
||||
.. monitoring-event:: NO_EVENTS
|
||||
|
||||
An alias for ``0`` so users can do explict comparisions like::
|
||||
An alias for ``0`` so users can do explicit comparisons like::
|
||||
|
||||
if get_events(DEBUGGER_ID) == NO_EVENTS:
|
||||
...
|
||||
|
|
Loading…
Reference in New Issue