diff --git a/changelog.rst b/changelog.rst index b05af62b5fb..974890264d1 100644 --- a/changelog.rst +++ b/changelog.rst @@ -2385,7 +2385,7 @@ Fixed Documentation - `e385d28 `_ #3503 file extension correction xfliff to xliff (nixilla) - `6d34aa6 `_ #3478 Update custom_password_authenticator.rst (piotras-s) - `a171700 `_ #3477 Api key user provider should use "implements" instead of "extends" (skowi) -- `7fe0de3 `_ #3475 Fixed doc for framework.session.cookie_lifetime refrence. (tyomo4ka) +- `7fe0de3 `_ #3475 Fixed doc for framework.session.cookie_lifetime reference. (tyomo4ka) - `8155e4c `_ #3473 Update proxy_examples.rst (AZielinski) Minor Documentation Changes diff --git a/components/validator.rst b/components/validator.rst index 3081a5bc7e0..2ff7e75503c 100644 --- a/components/validator.rst +++ b/components/validator.rst @@ -23,7 +23,7 @@ Usage The Validator component behavior is based on two concepts: -* Contraints, which define the rules to be validated; +* Constraints, which define the rules to be validated; * Validators, which are the classes that contain the actual validation logic. The following example shows how to validate that a string is at least 10 diff --git a/http_cache.rst b/http_cache.rst index fc102790233..e1119434195 100644 --- a/http_cache.rst +++ b/http_cache.rst @@ -290,7 +290,7 @@ two things: (e.g. deleting a blog post). Caching them would prevent certain requests from hitting and mutating your application. -* POST requests are generally considered uncachable, but `they can be cached`_ +* POST requests are generally considered uncacheable, but `they can be cached`_ when they include explicit freshness information. However POST caching is not widely implemented, so you should avoid it if possible.