bpo-36168: Lowercase the word "subsequent" in get_value doc (GH-14485)
Subsequent -> subsequent
https://bugs.python.org/issue36168
(cherry picked from commit 12b436e3b0
)
Co-authored-by: Krishna Oza <krishoza15sep@gmail.com>
This commit is contained in:
parent
2683ded568
commit
59ec9ee4d7
|
@ -146,7 +146,7 @@ implementation as the built-in :meth:`~str.format` method.
|
|||
keyword arguments.
|
||||
|
||||
For compound field names, these functions are only called for the first
|
||||
component of the field name; Subsequent components are handled through
|
||||
component of the field name; subsequent components are handled through
|
||||
normal attribute and indexing operations.
|
||||
|
||||
So for example, the field expression '0.name' would cause
|
||||
|
|
Loading…
Reference in New Issue