From a59800d98c9a4a3cd1d2b275948ada2a93e43cd9 Mon Sep 17 00:00:00 2001
From: Lorenzo Campanile <lorenzo_campanile@virgilio.it>
Date: Fri, 6 Jan 2023 15:28:57 +0100
Subject: [PATCH 1/2] added notes to the DTO doc, about serialization

As now, it's not very clear that the serialization process with groups is involved.
The phrase "In some cases, using an input DTO is a way to avoid serialization groups." can be misleading.

Thank you!
---
 core/dto.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/core/dto.md b/core/dto.md
index 757a8f45ff9..e52065b7a5d 100644
--- a/core/dto.md
+++ b/core/dto.md
@@ -22,6 +22,8 @@ final class UserResetPasswordDto
 }
 ```
 
+**Note**: if you have any *denormalizationContext* on the *User* entity (or just the entity *Post* operation), make sure to annotate the fields in the DTO class accordingly.
+
 ```php
 <?php
 // api/src/Model/User.php
@@ -88,6 +90,8 @@ This will dispatch the `App\Dto\Message` via [Symfony Messenger](https://symfony
 
 To return another representation of your data in a [State Provider](./state-providers.md) we advise to specify the `output` attribute of the resource. Note that this technique works without any changes to the resource but your API documentation would be wrong.
 
+**Note**: if you have any *normalizationContext* on the *User* entity (or just the entity *Get* operation), make sure to annotate the fields in the DTO class accordingly.
+
 ```php
 <?php
 

From a3de1665b75a91a588d56279845a1ec9d33302a1 Mon Sep 17 00:00:00 2001
From: Lorenzo Campanile <lorenzo_campanile@virgilio.it>
Date: Fri, 6 Jan 2023 15:35:19 +0100
Subject: [PATCH 2/2] fixed previous note on the dto page

---
 core/dto.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/dto.md b/core/dto.md
index e52065b7a5d..97ddf292188 100644
--- a/core/dto.md
+++ b/core/dto.md
@@ -22,7 +22,7 @@ final class UserResetPasswordDto
 }
 ```
 
-**Note**: if you have any *denormalizationContext* on the *User* entity (or just the entity *Post* operation), make sure to annotate the fields in the DTO class accordingly.
+**Note**: if you have any *denormalizationContext* groups on the *User* entity (or just on the entity *Post* operation), make sure to annotate the fields in the DTO class accordingly.
 
 ```php
 <?php
@@ -90,7 +90,7 @@ This will dispatch the `App\Dto\Message` via [Symfony Messenger](https://symfony
 
 To return another representation of your data in a [State Provider](./state-providers.md) we advise to specify the `output` attribute of the resource. Note that this technique works without any changes to the resource but your API documentation would be wrong.
 
-**Note**: if you have any *normalizationContext* on the *User* entity (or just the entity *Get* operation), make sure to annotate the fields in the DTO class accordingly.
+**Note**: if you have any *normalizationContext* groups on the *User* entity (or just on the entity *Get* operation), make sure to annotate the fields in the DTO class accordingly.
 
 ```php
 <?php