fix(wording): fix on injection name & code style

Author: Guikingone

service_container/injection_types.rst

@@ -249,10 +249,10 @@ But, it is useful to know that this can be done with the service container,
 especially if you are working with code that is out of your control, such
 as in a third party library, which uses public properties for its dependencies.
 
-Static Injection
-----------------
+Immutable Injection
+-------------------
 
-Another possible injection in to use a method which return `static`, 
+Another possible injection in to use a method which return ``static``,
 this approach allow you to make a service immutable::
 
     // ...
@@ -347,9 +347,9 @@ so, what are the advantages?
 The disadvantages are:
 
 * As the ``@return static`` docblock is required by the container to
-  understand that the method return a new object, you can
-  found that adding docblock for a single method isn't adapted or
-  can tie your code to the container.
+  understand that the method return a new object,
+  you can found that adding docblock for a single method isn't adapted or
+  link your code to the container.
 
 * As this approach force the container to create a new object
   once the method is called, you can found hard to debug and test your code.