- `e385d28 <https://github.com/symfony/symfony-docs/commit/e385d28bee7c7418c8175d43befc4954a43a300c>`_ #3503 file extension correction xfliff to xliff (nixilla)

- `6d34aa6 <https://github.com/symfony/symfony-docs/commit/6d34aa6038b8317259d2e8fffd186ad24fef5bc5>`_ #3478 Update custom_password_authenticator.rst (piotras-s)

- `a171700 <https://github.com/symfony/symfony-docs/commit/a171700fb8d9695947bc1b16c6f61c183f296657>`_ #3477 Api key user provider should use "implements" instead of "extends" (skowi)

- `8155e4c <https://github.com/symfony/symfony-docs/commit/8155e4cab70e481962a4775274a4412a4465ecdc>`_ #3473 Update proxy_examples.rst (AZielinski)

Minor Documentation Changes

The Validator component behavior is based on two concepts:

* 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

(e.g. deleting a blog post). Caching them would prevent certain requests from hitting

and mutating your application.

when they include explicit freshness information. However POST caching is not

widely implemented, so you should avoid it if possible.