diff --git a/core/content-negotiation.md b/core/content-negotiation.md
index 7194b60c855..d03cd75d931 100644
--- a/core/content-negotiation.md
+++ b/core/content-negotiation.md
@@ -356,7 +356,7 @@ merge new encoders and normalizers in API Platform.
 ## JSON:API sparse fieldset and sort parameters
 
 > [!WARNING]  
-> The SortFilter is for Eloquent, the Doctrine equivalent is the OrderFilter. 
+> The SortFilter is for Eloquent, the Doctrine equivalent is the OrderFilter.
 > The config/api-platform.php is Laravel specific.
 
 When working with JSON:API you may want to declare the `SparseFieldset` and the
@@ -371,11 +371,11 @@ use ApiPlatform\JsonApi\Filter\SparseFieldset;
 use ApiPlatform\Laravel\Eloquent\Filter\JsonApi\SortFilter;
 
 return [
-	// ...
-	'parameters' => [
-		new QueryParameter(key: 'fields', filter: SparseFieldset::class),
-		new QueryParameter(key: 'sort', filter: SortFilter::class),
-	],
+    // ...
+    'parameters' => [
+        new QueryParameter(key: 'fields', filter: SparseFieldset::class),
+        new QueryParameter(key: 'sort', filter: SortFilter::class),
+    ],
 ];
 ```
 
diff --git a/core/elasticsearch.md b/core/elasticsearch.md
index 370085e987e..53b9db80951 100644
--- a/core/elasticsearch.md
+++ b/core/elasticsearch.md
@@ -8,7 +8,7 @@ application search, security analytics, metrics, logging, etc.
 API Platform comes natively with the **reading** support for Elasticsearch. It uses internally the official PHP client
 for Elasticsearch: [Elasticsearch-PHP](https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/index.html).
 
-Be careful, API Platform only supports Elasticsearch >= 7.11.0 < 8.0 and Elasticsearch >= 8.4 < 9.0. Support for 
+Be careful, API Platform only supports Elasticsearch >= 7.11.0 < 8.0 and Elasticsearch >= 8.4 < 9.0. Support for
 Elasticsearch 8 was introduced in API Platform 3.2.
 
 ## Enabling Reading Support
diff --git a/core/errors.md b/core/errors.md
index 923e05d0f18..2bc78da84b7 100644
--- a/core/errors.md
+++ b/core/errors.md
@@ -330,7 +330,7 @@ Since 3.4, you also have the possibility to link your specific domain exceptions
 directly in your OpenAPI definition !
 
 Let's say that you have a `Greetings` resource, and that one of its providers can throw the following exception for the
-`ApiPlatform\Metadata\GetCollection` Operation: 
+`ApiPlatform\Metadata\GetCollection` Operation:
 
 ```php
 use ApiPlatform\Metadata\ErrorResource;
@@ -369,7 +369,7 @@ class MyDomainException extends \Exception implements ProblemExceptionInterface
 ```
 
 As long as your Exception implements `ApiPlatform\Metadata\Exception\ProblemExceptionInterface` and has the `ErrorResource`
-attribute, you can then map it to your Operation this way: 
+attribute, you can then map it to your Operation this way:
 
 ```php
 use ApiPlatform\Metadata\ApiResource;
diff --git a/extra/releases.md b/extra/releases.md
index 50655968081..37f68ddaadd 100644
--- a/extra/releases.md
+++ b/extra/releases.md
@@ -10,8 +10,8 @@ For example:
 - version 3.2 has been released on 12 October 2023;
 - version 3.3 has been released on 9 April 2024 (we were a little late, it should have been published in March);
 - versions 3.4 has been released on 18 September 2024;
-- versions 4.0 has been released on 27 September 2024; 
-- versions 4.1 has been released on 28 February 2025; 
+- versions 4.0 has been released on 27 September 2024;
+- versions 4.1 has been released on 28 February 2025;
 
 ## Maintenance
 
diff --git a/symfony/file-upload.md b/symfony/file-upload.md
index 5321853242b..40b2624ed91 100644
--- a/symfony/file-upload.md
+++ b/symfony/file-upload.md
@@ -100,7 +100,8 @@ use Vich\UploaderBundle\Mapping\Annotation as Vich;
                         ]
                     ])
                 )
-            )
+            ),
+            deserialize: false
         )
     ]
 )]