uppercase "dependency injection"

best_practices/introduction.rst

@@ -62,8 +62,8 @@ Symfony to follow everything. If you are totally new to Symfony, welcome!
 Start with :doc:`The Quick Tour </quick_tour/the_big_picture>` tutorial first.
 
 We've deliberately kept this guide short. We won't repeat explanations that
-you can find in the vast Symfony documentation, like discussions about dependency
-injection or front controllers. We'll solely focus on explaining how to do
+you can find in the vast Symfony documentation, like discussions about Dependency
+Injection or front controllers. We'll solely focus on explaining how to do
 what you already know.
 
 The Application

book/page_creation.rst

@@ -763,7 +763,7 @@ of the most common elements of a bundle:
     Contains the controllers of the bundle (e.g. ``RandomController.php``).
 
 ``DependencyInjection/``
-    Holds certain dependency injection extension classes, which may import service
+    Holds certain Dependency Injection Extension classes, which may import service
     configuration, register compiler passes or more (this directory is not
     necessary).
 

book/testing.rst

@@ -455,8 +455,8 @@ Accessing the Container
 
 It's highly recommended that a functional test only tests the Response. But
 under certain very rare circumstances, you might want to access some internal
-objects to write assertions. In such cases, you can access the dependency
-injection container::
+objects to write assertions. In such cases, you can access the Dependency
+Injection Container::
 
     $container = $client->getContainer();
 

cookbook/routing/service_container_parameters.rst

@@ -127,5 +127,5 @@ path):
 
 .. seealso::
 
-    For parameter handling within a Dependency Injection class see
+    For parameter handling within a Dependency Injection Class see
     :doc:`/cookbook/configuration/using_parameters_in_dic`.

cookbook/validation/custom_constraint.rst

@@ -159,8 +159,8 @@ Constraint Validators with Dependencies
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If your constraint validator has dependencies, such as a database connection,
-it will need to be configured as a service in the dependency injection
-container. This service must include the ``validator.constraint_validator``
+it will need to be configured as a service in the Dependency Injection
+Container. This service must include the ``validator.constraint_validator``
 tag and an ``alias`` attribute:
 
 .. configuration-block::