Fix info in manual

Author: Jon Acker

README.md

@@ -107,7 +107,7 @@ $container = Mage::helper('inviqa_symfonyContainer/containerProvider')->getConta
 ### Test Environment
 The configuration builder reads the magento configuration node "global/environment" and uses this to switch the container generator to test environment. The string expected in "global/environment" node is "test". In this mode, the container generator will read addtiaional services_test.xml files, which will override services defined in services.xml if their id's match. In this way, you can use "mock" services for integration testing purposes. (see additional documentation in https://github.com/inviqa/symfony-container-generator)
 
-### Providing Magento Store Config Values to Service Constructors (since version 0.5.0)
+### Providing Magento Store Config Values to Service Constructors
 If your service requires a value from the store config, something which would normaly require calling Mage::getStoreConfig('web/secure/base_url') for example, you can use the special tag mage.config in place of an <argument> node in your service definition. The "key" attribute is a regular magento store config key. This will simply add the value of requested store config to the list of service constructor arguments:
 
 ```xml
@@ -134,7 +134,7 @@ class Acme_Service
 
 If the specified key does not exist, or is empty, the argument will be null or empty.
 
-### Explicitly Providing Dependencies via __dependencies
+### Explicitly Providing Dependencies via __dependencies (since version 0.5.0)
 
 Certain Magento classes, such as controllers, observers and blocks are instantiated by the system and therefore cannot be instantiated by the DI Container, nevertheless an additional service tag can make it easier to explicitly provide dependencies to these classes. Adding the mage.injectable tag to a service will allow you to provide this services dependencies *after* the service has been instantiated. The services arguments will be provided to the __dependencies method provided you call ServiceInjector::setupDependencies($class) after service instantiation, and your service has a __dependencies method that contains typehints that match the arguments type an order.