From 58cd3ae112abf36fcd8c1cdf2a55e21b3a5734d3 Mon Sep 17 00:00:00 2001 From: esteevens Date: Fri, 25 Oct 2024 08:17:00 +0200 Subject: [PATCH] Fix tiny typo in glossary.md (#1363) --- docs/glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/glossary.md b/docs/glossary.md index 3fd50c24..45fca368 100644 --- a/docs/glossary.md +++ b/docs/glossary.md @@ -113,7 +113,7 @@ field However, with the emergence of {mod}`dataclasses`, [Pydantic](https://docs.pydantic.dev/latest/concepts/fields/), and other libraries, the term "field" has become a common term for a predefined attribute on a class in the Python ecosystem. - So with out new APIs, we've embraced it too by calling the function to create them {func}`attrs.field`, and use the term "field" throughout the documentation interchangeably. + So with our new APIs, we've embraced it too by calling the function to create them {func}`attrs.field`, and use the term "field" throughout the documentation interchangeably. See also {doc}`names`.