fix(dotrine/filters): typo and missing part for ODM

Author: vinceAmstoutz

core/doctrine-filters.md

@@ -183,7 +183,7 @@ services all begin with `api_platform.doctrine_mongodb.odm`.
 To add some search filters, choose over this new list:
 - [IriFilter](#iri-filter) (filter on IRIs)
 - [ExactFilter](#exact-filter) (filter with exact value)
-- [PartialSearchFilter](#partial-search-filter) (filter using a `LIKE %value%``)
+- [PartialSearchFilter](#partial-search-filter) (filter using a `LIKE %value%`)
 - [FreeTextQueryFilter](#free-text-query-filter) (allows you to apply multiple filters to multiple properties of a resource at the same time, using a single parameter in the URL)
 - [OrFilter](#or-filter) (apply a filter using `orWhere` instead of `andWhere` )
 
@@ -1456,7 +1456,7 @@ class MyCustomFilter implements FilterInterface
     }
 }
 ```
-#### Implementing a Custom Filter
+#### Implementing a Custom ORM Filter
 
 Let's create a concrete filter that allows fetching entities based on the month of a date field (e.g., `createdAt`).
 
@@ -1497,8 +1497,8 @@ class MonthFilter implements FilterInterface
 }
 ```
 
-Now that the filter is created, it must be associated with an API resource. We use the `#[QueryParameter]` attribute on
-a `GetCollection` operation for this. For other syntax please refer to the [documentation](#introduction).
+Now that the filter is created, it must be associated with an API resource. We use the `QueryParameter` object on
+a `#[GetCollection]` operation attribute for this. For other syntax please refer to [this documentation](#introduction).
 
 ```php
 <?php
@@ -1524,8 +1524,11 @@ class Invoice
 }
 ```
 
-And that's it! ✅ Your filter is operational. A request like `GET /invoices?createdAtMonth=7` will now correctly return
-the invoices from July!
+And that's it! ✅ 
+
+Your filter is operational. 
+
+A request like `GET /invoices?createdAtMonth=7` will now correctly return the invoices from July!
 
 #### Adding Custom Filter ORM Validation And A Better Typing
 
@@ -1964,10 +1967,8 @@ class MonthFilter implements FilterInterface
 }
 ```
 
-Now that the filter is created, it must be associated with an API resource. We use the `#[QueryParameter]` attribute on
-a `GetCollection` operation for this. For other synthax please refer to
-
-[//]: # (TODO: add link to synthax)
+Now that the filter is created, it must be associated with an API resource. We use the `QueryParameter` object on
+a `#[GetCollection]` operation attribute for this. For other synthax please refer to [this documentation](#introduction).
 
 ```php
 <?php
@@ -1993,7 +1994,11 @@ class Invoice
 }
 ```
 
-And that's it! ✅ Your filter is operational. A request like `GET /invoices?createdAtMonth=7` will now correctly return
+And that's it! ✅ 
+
+Your filter is operational. 
+
+A request like `GET /invoices?createdAtMonth=7` will now correctly return
 the invoices from July!
 
 #### Adding Custom Filter ODM Validation And A Better Typing
@@ -2003,6 +2008,18 @@ To validate inputs and ensure the correct type, we can implement the `JsonSchema
 
 This allows delegating validation to API Platform, respecting the [SOLID Principles](https://en.wikipedia.org/wiki/SOLID).
 
+> [!NOTE]
+> Even with our internal systems, some additional **manual validation** is needed to ensure greater accuracy. However,
+> we already take care of a lot of these validations for you.
+>
+> You can see how this works directly in our code components:
+>
+> * The `ParameterValidatorProvider` for **Symfony** can be found [here](https://github.com/api-platform/core/blob/c9692b509d5b641104addbadb349b9bcab83e251/src/Symfony/Validator/State/ParameterValidatorProvider.php).
+> * The `ParameterValidatorProvider` for **Laravel** is located [here](https://github.com/api-platform/core/blob/c9692b509d5b641104addbadb349b9bcab83e251/src/Laravel/State/ParameterValidatorProvider.php).
+>
+> Additionally, we filter out empty values within our `ParameterExtension` classes. For instance, the **Doctrine ODM**
+> `ParameterExtension` [handles this filtering here](https://github.com/api-platform/core/blob/c9692b509d5b641104addbadb349b9bcab83e251/src/Doctrine/Odm/Extension/ParameterExtension.php#L50-L52).
+
 ```php
 <?php
 
@@ -2029,10 +2046,17 @@ final class MonthFilter implements FilterInterface, JsonSchemaFilterInterface
 }
 ```
 
-With this code, under the hood, API Platform has added a [Symfony Range constraint](https://symfony.com/doc/current/reference/constraints/Range.html)
-that only accepts values between `1` and `12` (inclusive), which is what we want. In addition, we map the value to an integer,
-which allows us to reject other types and directly return an integer in our filter when we retrieve the value with
-`$monthValue = $parameter->getValue();`.
+With this code, under the hood, API Platform automatically adds a [Symfony Range constraint](https://symfony.com/doc/current/reference/constraints/Range.html).
+This ensures the parameter only accepts values between `1` and `12` (inclusive), which is exactly what we need.
+
+This approach offers two key benefits:
+
+- Automatic Validation: It rejects other data types and invalid values, so you get an integer directly.
+- Simplified Logic: You can retrieve the value with `$monthValue = $parameter->getValue();` knowing it's already a
+- validated integer.
+
+This means you **don't have to add custom validation to your filter class, entity, or model**. The validation is handled
+for you, making your code cleaner and more efficient.
 
 ### Documenting the ODM Filter (OpenAPI)