docs: apply suggestions

docs/migration.md

@@ -239,7 +239,7 @@ See [Model Config](usage/model_config.md) for more details.
         example, despite the fact that the validator below will never error, the following code raises a `ValidationError`:
 
 !!! note
-    To avoid this, you can use the `validate_default` argument in the `Field` function. When set to `True`, it mimics the behavior of `always=True` in pydantic v1. However, the new way of using `validate_default` is encouraged as it provides more flexibility and control.
+    To avoid this, you can use the `validate_default` argument in the `Field` function. When set to `True`, it mimics the behavior of `always=True` in Pydantic v1. However, the new way of using `validate_default` is encouraged as it provides more flexibility and control.
 
 
 ```python test="skip"

docs/usage/validators.md

@@ -266,7 +266,7 @@ print(context['logs'])
 
 Validators won't run when the default value is used.
 This applies both to `@field_validator` validators and `Annotated` validators.
-You can force them to run with `Field(validate_defaults=True)`. Setting `validate_default` to `True` has the closest behavior to using `always=True` in `validator` in pydantic v1. However, you are generally better off using a `@model_validator(mode='before')` where the function is called before the inner validator is called.
+You can force them to run with `Field(validate_defaults=True)`. Setting `validate_default` to `True` has the closest behavior to using `always=True` in `validator` in Pydantic v1. However, you are generally better off using a `@model_validator(mode='before')` where the function is called before the inner validator is called.
 
 
 ```py