From f7feb0fa48c29cf84cd6d554404a472fad4787a6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Timoth=C3=A9e=20Mazzucotelli?= Date: Mon, 28 Aug 2023 14:48:16 +0200 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20Fix=20typos=20in=20`typing?= =?UTF-8?q?=5Fdoc`=20page=20(#10162)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- typing_doc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/typing_doc.md b/typing_doc.md index e8cc1f005..97eff22d1 100644 --- a/typing_doc.md +++ b/typing_doc.md @@ -113,7 +113,7 @@ When creating a type alias, like: Username = Annotated[str, doc("The name of a user in the system")] ``` -...the documentation would be considered to be carried by the parameter annotated with `Foo`. +...the documentation would be considered to be carried by the parameter annotated with `Username`. So, in a function like: @@ -127,7 +127,7 @@ def hi(to: Username) -> None: ... def hi(to: Annotated[str, doc("The name of a user in the system")]) -> None: ... ``` -Nevertheless, implementers would not be required to support type aliases outside of the final type annotation to be conformant with this specification, as it could require more complex derefrenecing logic. +Nevertheless, implementers would not be required to support type aliases outside of the final type annotation to be conformant with this specification, as it could require more complex dereferencing logic. #### Annotating Type Parameters