Tweaks and minor rewords

Author: javiereguiluz

components/serializer.rst

@@ -1207,9 +1207,8 @@ Option          Description                                               Defaul
 Context Builders
 ----------------
 
-Context builders are objects that help creating the :ref:`serialization context <serializer-context>`.
-
-You can easily use context builders by instantiating them::
+Instead of passing plain PHP arrays to the :ref:`serialization context <serializer-context>`,
+you can use "context builders" to define the context using a fluent interface::
 
     use Symfony\Component\Serializer\Context\Encoder\CsvEncoderContextBuilder;
     use Symfony\Component\Serializer\Context\Normalizer\ObjectNormalizerContextBuilder;
@@ -1228,14 +1227,18 @@ You can easily use context builders by instantiating them::
 
     $serializer->serialize($something, 'csv', $contextBuilder->toArray());
 
+.. versionadded:: 6.1
+
+    Context builders were introduced in Symfony 6.1.
+
 .. note::
 
     The Serializer component provides a context builder
     for each :ref:`normalizer <component-serializer-normalizers>`
     and :ref:`encoder <component-serializer-encoders>`.
 
-    You can also create custom context builders to deal with your
-    context values. Read more at :doc:`/serializer/custom_context_builders`.
+    You can also :doc:`create custom context builders </serializer/custom_context_builders>`
+    to deal with your context values.
 
 Skipping ``null`` Values
 ------------------------

serializer.rst

@@ -156,20 +156,22 @@ configuration:
 Using Context Builders
 ----------------------
 
-To define a proper (de)serialization context, you can leverage context builders.
-Those are objects that help you to create that context by providing
-auto-completion, validation, and documentation::
+.. versionadded:: 6.1
+
+    Context builders were introduced in Symfony 6.1.
+
+To define the (de)serialization context, you can use "context builders", which
+are objects that help you to create that context by providing autocompletion,
+validation, and documentation::
 
     use Symfony\Component\Serializer\Context\Normalizer\DateTimeNormalizerContextBuilder;
 
     $contextBuilder = (new DateTimeNormalizerContextBuilder())->withFormat('Y-m-d H:i:s');
-
     $serializer->serialize($something, 'json', $contextBuilder->toArray());
 
 Each normalizer/encoder has its related :ref:`context builder <component-serializer-context-builders>`.
-To create a full (de)serialization context, you will be able to chain them using the
-``withContext`` method. As the ``withContext`` method takes an array as an argument, it is
-also possible to pass custom values to that context::
+To create a more complex (de)serialization context, you can chain them using the
+``withContext()`` method::
 
     use Symfony\Component\Serializer\Context\Encoder\CsvEncoderContextBuilder;
     use Symfony\Component\Serializer\Context\Normalizer\ObjectNormalizerContextBuilder;
@@ -188,8 +190,8 @@ also possible to pass custom values to that context::
 
     $serializer->serialize($something, 'csv', $contextBuilder->toArray());
 
-If you want auto-completion, validation, and documentation for your custom context values,
-you can :doc:`create your context builders </serializer/custom_context_builders>`.
+You can also :doc:`create your context builders </serializer/custom_context_builders>`
+to have autocompletion, validation, and documentation for your custom context values.
 
 .. _serializer-using-serialization-groups-annotations:
 

serializer/custom_context_builders.rst

@@ -4,22 +4,25 @@
 How to Create your Custom Context Builder
 =========================================
 
+.. versionadded:: 6.1
+
+    Context builders were introduced in Symfony 6.1.
+
 The :doc:`Serializer Component </components/serializer>` uses Normalizers
 and Encoders to transform any data to any data-structure (e.g. JSON).
-That serialization process could be configured thanks to a
+That serialization process can be configured thanks to a
 :ref:`serialization context <serializer-context>`, which can be built thanks to
 :ref:`context builders <component-serializer-context-builders>`.
 
-Each built-in normalizer/encoder has its related context builder.
-But, as an example, you may want to use custom context values
-for your :doc:`custom normalizers </serializer/custom_normalizer>`
-and create a custom context builder related to them.
+Each built-in normalizer/encoder has its related context builder. However, you
+may want to create a custom context builder for your
+:doc:`custom normalizers </serializer/custom_normalizer>`.
 
-Creating a new context builder
+Creating a new Context Builder
 ------------------------------
 
 Let's imagine that you want to handle date denormalization differently if they
-are coming from a legacy system, by converting them to ``null`` if the serialized
+are coming from a legacy system, by converting dates to ``null`` if the serialized
 value is ``0000-00-00``. To do that you'll first have to create your normalizer::
 
     // src/Serializer/ZeroDateTimeDenormalizer.php
@@ -51,14 +54,13 @@ value is ``0000-00-00``. To do that you'll first have to create your normalizer:
         }
     }
 
-You'll therefore be able to cast zero-ish dates to ``null`` during denormalization::
+Now you can cast zero-ish dates to ``null`` during denormalization::
 
     $legacyData = '{"updatedAt": "0000-00-00"}';
-
     $serializer->deserialize($legacyData, MyModel::class, 'json', ['zero_datetime_to_null' => true]);
 
-Then, if you don't want other developers to have to remind the precise ``zero_date_to_null`` context key,
-you can create a dedicated context builder::
+Now, to avoid having to remember about this specific ``zero_date_to_null``
+context key, you can create a dedicated context builder::
 
     // src/Serializer/LegacyContextBuilder
     namespace App\Serializer;
@@ -75,7 +77,7 @@ you can create a dedicated context builder::
         }
     }
 
-And finally use it to build the serialization context::
+And finally, use it to build the serialization context::
 
     $legacyData = '{"updatedAt": "0000-00-00"}';