Updates according to code updates

Author: mtarld

service_container/service_decoration.rst

@@ -317,7 +317,7 @@ Control the behavior when the decorated service does not exist
 --------------------------------------------------------------
 
 Let's imagine you have a decorator that decorates a service defined in another bundle.
-If for some reasons, that bundle is missing, the ``decoration_on_decorated_invalid``
+If for some reasons, that bundle is missing, the ``decoration_on_invalid``
 option will allow you to handle the lack of decorated service.
 
 .. configuration-block::
@@ -330,7 +330,7 @@ option will allow you to handle the lack of decorated service.
         Bar:
             public: false
             decorates: Foo
-            decoration_on_decorated_invalid: ignore
+            decoration_on_invalid: ignore
             arguments: ['@Bar.inner']
 
     .. code-block:: xml
@@ -345,7 +345,7 @@ option will allow you to handle the lack of decorated service.
             <services>
                 <service id="Foo"/>
 
-                <service id="Bar" decorates="Foo" decoration-on-decorated-invalid="ignore">
+                <service id="Bar" decorates="Foo" decoration-on-invalid="ignore">
                     <argument type="service" id="Bar.inner"/>
                 </service>
             </services>
@@ -377,14 +377,28 @@ Three different behaviors are available:
 
 * ``exception``: The default behavior. When used, a ``ServiceNotFoundException``
   will be thrown telling that decorator's dependency is missing.
-* ``ignored``: Using that behavior, the container will remove either decorator
+* ``ignore``: Using that behavior, the container will remove either decorator
   and decorated services.
-* ``nulled``: When used, the container will keep the decorator
+* ``null``: When used, the container will keep the decorator
   service and will set the decorated one to `null`.
 
+.. note::
+
+    If you are using yaml to describe your services, please ensure that
+    ``null`` value is wrapped with quotes. In fact in yaml, ``null`` will be interpreted
+    as the null value and not as the null string. Therefore, the compiler will throw
+    an ``InvalidArgumentException``
+
+    .. code-block:: yaml
+
+        Foo:
+            decorates: Foo
+            decoration_on_invalid: 'null'
+            arguments: ['@Bar.inner']
+
 .. tip::
 
-    When using ``nulled``, you may update the decorator's constructor in
+    When using ``null``, you may update the decorator's constructor in
     order to make decorated dependency nullable. In this way, you will be able to
     check the presence of decorated service in other methods.