we>you, php>PHP, fixed directive start & list style

Author: Iltar van der Berg

cookbook/controller/argument_value_resolver.rst

@@ -31,6 +31,7 @@ Symfony ships with four value resolvers in the HttpKernel:
    When the action is called, the last (variadic) argument will contain all the values of this array.
 
 .. note::
+
     In older versions of Symfony this logic was all resolved within the ``ControllerResolver``. The
     old functionality is moved to the ``LegacyArgumentResolver``, which contains the previously
     used resolving logic.
@@ -39,7 +40,7 @@ Adding a New Value Resolver
 ---------------------------
 
 Adding a new value resolver requires one class and one service defintion. In our next example, we
-will be creating a shortcut to inject the ``User`` object from our security. Given we write the following
+will be creating a shortcut to inject the ``User`` object from our security. Given you write the following
 action::
 
     namespace AppBundle\Controller;
@@ -52,37 +53,38 @@ action::
         }
     }
 
-Somehow we will have to get the ``User`` object and inject it into our action. This can be done
+Somehow you will have to get the ``User`` object and inject it into our action. This can be done
 by implementing the :class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentValueResolverInterface`.
-This interface specifies that we have to implement two methods::
+This interface specifies that you have to implement two methods::
 
     interface ArgumentValueResolverInterface
     {
         public function supports(Request $request, ArgumentMetadata $argument);
         public function resolve(Request $request, ArgumentMetadata $argument);
     }
 
- - The ``supports()`` method is used to check whether the resolver supports the given argument. It will
+  * The ``supports()`` method is used to check whether the resolver supports the given argument. It will
    only continue if it returns ``true``.
 
- - The ``resolve()`` method will be used to resolve the actual value just acknowledged by
+  * The ``resolve()`` method will be used to resolve the actual value just acknowledged by
    ``supports()``. Once a value is resolved you can ``yield`` the value to the ``ArgumentResolver``.
 
- - The ``Request`` object is the current ``Request`` which would also be injected into your
+  * The ``Request`` object is the current ``Request`` which would also be injected into your
    action in the forementioned functionality.
 
- - The :class:``Symfony\\Component\\HttpKernel\\ControllerMetadata\\ArgumentMetadata`` represents
+  * The :class:``Symfony\\Component\\HttpKernel\\ControllerMetadata\\ArgumentMetadata`` represents
    information retrieved from the method signature for the current argument it's trying to resolve.
 
 .. note::
+
     The ``ArgumentMetadata`` is a simple data container created by the
     :class:``Symfony\\Component\\HttpKernel\\ControllerMetadata\\ArgumentMetadataFactory``. This
-    factory will work on every supported php version but might give different results. E.g. the
-    ``isVariadic()`` will never return true on php 5.5 and only on php 7.0 and higher it will give
+    factory will work on every supported PHP version but might give different results. E.g. the
+    ``isVariadic()`` will never return true on PHP 5.5 and only on PHP 7.0 and higher it will give
     you basic types when calling ``getType()``.
 
-Now that we know what to do, we can implement this interface. In order to get the current ``User``,
-we will have to get it from the ``TokenInterface`` which is in the ``TokenStorageInterface``::
+Now that you know what to do, you can implement this interface. In order to get the current ``User``,
+you will have to get it from the ``TokenInterface`` which is in the ``TokenStorageInterface``::
 
     namespace AppBundle\ArgumentValueResolver;
 
@@ -110,10 +112,11 @@ we will have to get it from the ``TokenInterface`` which is in the ``TokenStorag
         }
     }
 
-This was pretty simple, now all we have to do is add the configuration for the service container. This
+This was pretty simple, now all you have to do is add the configuration for the service container. This
 can be done by tagging the service with ``kernel.argument_resolver`` and adding a priority.
 
 .. note::
+
     While adding a priority is optional, it's recommended to add one to make sure the expected
     value is injected. The ``ArgumentFromAttributeResolver`` has a priority of 100. As this
     one is responsible for fetching attributes from the ``Request``, it's also recommended to