[3.11] Fix typos in documentation and comments (GH-102374) (#102376)

[3.11] Fix typos in documentation and comments (GH-102374)

Found some duplicate `to`s in the documentation and some code comments and fixed them.

[Misc/NEWS.d/3.12.0a1.rst](ed55c69ebd/Misc/NEWS.d/3.12.0a1.rst) also contains two duplicate `to`s, but I wasn't sure if it's ok to touch that file.  Looks auto generated.  I'm happy to amend the PR if requested. :)

Automerge-Triggered-By: GH:AlexWaygood

Co-authored-by: Michael K <michael-k@users.noreply.github.com>
This commit is contained in:
Alex Waygood 2023-03-02 16:00:06 +00:00 committed by GitHub
parent 9a5f2e8562
commit 3b1201daf6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions

View file

@ -72,7 +72,7 @@ including `cursors`_ and `transactions`_.
First, we need to create a new database and open First, we need to create a new database and open
a database connection to allow :mod:`!sqlite3` to work with it. a database connection to allow :mod:`!sqlite3` to work with it.
Call :func:`sqlite3.connect` to to create a connection to Call :func:`sqlite3.connect` to create a connection to
the database :file:`tutorial.db` in the current working directory, the database :file:`tutorial.db` in the current working directory,
implicitly creating it if it does not exist: implicitly creating it if it does not exist:

View file

@ -1343,7 +1343,7 @@ These are not used in annotations. They are building blocks for creating generic
x: Ts # Not valid x: Ts # Not valid
x: tuple[Ts] # Not valid x: tuple[Ts] # Not valid
x: tuple[*Ts] # The correct way to to do it x: tuple[*Ts] # The correct way to do it
Type variable tuples can be used in the same contexts as normal type Type variable tuples can be used in the same contexts as normal type
variables. For example, in class definitions, arguments, and return types:: variables. For example, in class definitions, arguments, and return types::

View file

@ -302,7 +302,7 @@ class ZoneInfo(tzinfo):
# difference between utcoffset() and the "standard" offset, but # difference between utcoffset() and the "standard" offset, but
# the "base offset" and "DST offset" are not encoded in the file; # the "base offset" and "DST offset" are not encoded in the file;
# we can infer what they are from the isdst flag, but it is not # we can infer what they are from the isdst flag, but it is not
# sufficient to to just look at the last standard offset, because # sufficient to just look at the last standard offset, because
# occasionally countries will shift both DST offset and base offset. # occasionally countries will shift both DST offset and base offset.
typecnt = len(isdsts) typecnt = len(isdsts)