From 59ec9ee4d7f3c2444efb989e96f5124e1c246de5 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Mon, 1 Jul 2019 09:30:48 -0700 Subject: [PATCH] bpo-36168: Lowercase the word "subsequent" in get_value doc (GH-14485) Subsequent -> subsequent https://bugs.python.org/issue36168 (cherry picked from commit 12b436e3b079fb3e3a7197c089df90a77e3bdd77) Co-authored-by: Krishna Oza --- Doc/library/string.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/string.rst b/Doc/library/string.rst index 288dde6b3fe..af8b9b358cc 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