Tweaks

Author: javiereguiluz

components/dependency_injection.rst

@@ -170,10 +170,11 @@ like this::
 
     $newsletterManager = $containerBuilder->get('newsletter_manager');
 
-Behavior When Service Does Not Exist
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Getting Services That Don't Exist
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default, an exception is throw when a service does not exist. You can override the behavior by::
+By default, when you try to get a service that doesn't exist, you see an exception.
+You can override this behavior as follows::
 
     use Symfony\Component\DependencyInjection\ContainerBuilder;
     use Symfony\Component\DependencyInjection\ContainerInterface;
@@ -182,17 +183,22 @@ By default, an exception is throw when a service does not exist. You can overrid
 
     // ...
 
-    // the second argument is optional and define the behavior
+    // the second argument is optional and defines what to do when the service doesn't exist
     $newsletterManager = $containerBuilder->get('newsletter_manager', ContainerInterface::EXCEPTION_ON_INVALID_REFERENCE);
 
 
-Possible behaviors are:
+These are all the possible behaviors:
 
- * ``ContainerInterface::EXCEPTION_ON_INVALID_REFERENCE``: Throws an exception at compile time **default**
- * ``ContainerInterface::NULL_ON_INVALID_REFERENCE``:  Returns null
- * ``ContainerInterface::IGNORE_ON_INVALID_REFERENCE``: Ignores the wrapping command asking for the reference (for instance, ignore a setter if the service does not exist)
- * ``ContainerInterface::IGNORE_ON_UNINITIALIZED_REFERENCE``: Ignores/returns null for uninitialized services or invalid references
- * ``ContainerInterface::RUNTIME_EXCEPTION_ON_INVALID_REFERENCE``: Throws an exception at runtime, when trying to access the missing service
+ * ``ContainerInterface::EXCEPTION_ON_INVALID_REFERENCE``: throws an exception
+   at compile time (this is the **default** behavior);
+ * ``ContainerInterface::RUNTIME_EXCEPTION_ON_INVALID_REFERENCE``: throws an
+   exception at runtime, when trying to access the missing service;
+ * ``ContainerInterface::NULL_ON_INVALID_REFERENCE``: returns ``null``;
+ * ``ContainerInterface::IGNORE_ON_INVALID_REFERENCE``: ignores the wrapping
+   command asking for the reference (for instance, ignore a setter if the service
+   does not exist);
+ * ``ContainerInterface::IGNORE_ON_UNINITIALIZED_REFERENCE``: ignores/returns
+   ``null`` for uninitialized services or invalid references.
 
 Avoiding your Code Becoming Dependent on the Container
 ------------------------------------------------------