Minor tweaks

symfony · yceruto · Jul 2, 2018 · Oct 10, 2018 · Oct 12, 2018 · Nov 29, 2018
commit 5abcf6a25db9d04d7ba281d99c458bc5a870b8b1
diff --git a/components/options_resolver.rst b/components/options_resolver.rst
@@ -640,7 +640,7 @@ Nested Option
 .. versionadded:: 4.2
    This feature was introduced in Symfony 4.2.

-Suppose you want an option named ``spool`` which has two sub-options ``type``
+Suppose you have an option named ``spool`` which has two sub-options ``type``
 and ``path``. Instead of defining it as a simple array of values, you can pass
 a closure as the default value of the ``spool`` option with a :class:`Symfony\\Component\\OptionsResolver\\OptionsResolver`
 argument. Based on this instance, you can define the options under ``spool`` and its desired default
@@ -676,11 +676,11 @@ value::
        ),
    ));

-It allows you to create a nested options system with required options, validation (type, value),
-normalization and more.
+Also you can define required options, validation (type, value) and normalization of these
+nested options.

 If the default value of a child option depend on another option defined in parent level,
-adds a second ``Options`` argument to the closure::
+adds a second ``Options`` argument to the closure for access to them::

    class Mailer
    {
@@ -703,7 +703,7 @@ adds a second ``Options`` argument to the closure::
    The arguments of the closure must be type hinted as ``OptionsResolver`` and ``Options`` respectively.
    Otherwise, the closure itself is considered as the default value of the option.

-In same way, parent options can access the child option as follows::
+In same way, parent options can access to the child option as normal array::

    class Mailer
    {