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 <krishoza15sep@gmail.com>

diff --git a/Doc/library/string.rst b/Doc/library/string.rst
index 288dde6b3fe4c05aa7edb65cf137d84a33000716..af8b9b358cc388979396e309440c545674b4eada 100644 (file)
--- 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