From 43e9a51e23527c3344242718e4ab62d9c1da794d Mon Sep 17 00:00:00 2001 From: Varun Chawla Date: Sat, 7 Feb 2026 11:22:53 -0800 Subject: [PATCH] Fix typos in contributing and migration docs --- docs/en/docs/contributing.md | 2 +- docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/docs/contributing.md b/docs/en/docs/contributing.md index af7944e75..3a8165035 100644 --- a/docs/en/docs/contributing.md +++ b/docs/en/docs/contributing.md @@ -92,7 +92,7 @@ That way, you can edit the documentation/source files and see the changes live. /// tip -Alternatively, you can perform the same steps that scripts does manually. +Alternatively, you can perform the same steps that the script does manually. Go into the language directory, for the main docs in English it's at `docs/en/`: diff --git a/docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md b/docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md index fc90220b8..94147ccb1 100644 --- a/docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md +++ b/docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md @@ -130,6 +130,6 @@ First try with `bump-pydantic`, if your tests pass and that works, then you're d If `bump-pydantic` doesn't work for your use case, you can use the support for both Pydantic v1 and v2 models in the same app to do the migration to Pydantic v2 gradually. -You could fist upgrade Pydantic to use the latest version 2, and change the imports to use `pydantic.v1` for all your models. +You could first upgrade Pydantic to use the latest version 2, and change the imports to use `pydantic.v1` for all your models. Then, you can start migrating your models from Pydantic v1 to v2 in groups, in gradual steps. 🚶