Tweaks

javiereguiluz · javiereguiluz · commit 59576afa6e69 · 2023-10-04T13:25:17.000+02:00
diff --git a/components/property_info.rst b/components/property_info.rst
@@ -225,14 +225,15 @@ provide whether properties are readable or writable as booleans::
 The :class:`Symfony\\Component\\PropertyInfo\\Extractor\\ReflectionExtractor` looks
 for getter/isser/setter/hasser method in addition to whether or not a property is public
 to determine if it's accessible. This based on how the :doc:`PropertyAccess </components/property_access>`
-works. It assumes camel case style method names following `PSR-1`_. Therefore, a property like ``myProperty`` or ``my_property`` is
-readable if it has a ``getMyProperty()`` and writable if it has a ``setMyProperty()`` method.
+works. It assumes camel case style method names following `PSR-1`_. For example,
+both ``myProperty`` and ``my_property`` properties are readable if there's a
+``getMyProperty()`` method and writable if there's a ``setMyProperty()`` method.
 
 .. versionadded:: 6.4
 
-    Camel case style setter methods for properties in snake case (like ``my_property``) are accepted since Symfony 6.4. Before, the
-    setter name had to contain the underscores (e.g. `setMy_property()`) to make the property assumed writable.
-
+    In Symfony versions prior to 6.4, snake case properties (e.g. ``my_property``)
+    were not writable by camel case methods (e.g. ``setMyProperty()``). You had
+    to define method names with underscores (e.g. ``setMy_property()``).
 
 .. _property-info-initializable:
 
