diff options
author | Krishna Oza <krishoza15sep@gmail.com> | 2019-07-01 06:04:20 (GMT) |
---|---|---|
committer | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-07-01 06:04:20 (GMT) |
commit | 12b436e3b079fb3e3a7197c089df90a77e3bdd77 (patch) | |
tree | 6cfdac35bceeb2aaa4726fd6cf488806144dd08b | |
parent | c2cda638d63b98f5cf9a8ef13e15aace2b7e3f0b (diff) | |
download | cpython-12b436e3b079fb3e3a7197c089df90a77e3bdd77.zip cpython-12b436e3b079fb3e3a7197c089df90a77e3bdd77.tar.gz cpython-12b436e3b079fb3e3a7197c089df90a77e3bdd77.tar.bz2 |
bpo-36168: Lowercase the word "subsequent" in get_value doc (GH-14485)
Subsequent -> subsequent
https://bugs.python.org/issue36168
-rw-r--r-- | Doc/library/string.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/string.rst b/Doc/library/string.rst index 288dde6..af8b9b3 100644 --- a/Doc/library/string.rst +++ b/Doc/library/string.rst @@ -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 |