Merge pull request #1792 from greg0ire/fix_typo

weaverryan · weaverryan · commit 86cf8bfdaa05 · 2012-10-07T19:12:57.000-07:00
Various fixes on the dependency injection component documentation.
diff --git a/components/dependency_injection/compilation.rst b/components/dependency_injection/compilation.rst
@@ -287,7 +287,7 @@ will then be called when the container is compiled::
 
 .. note::
 
-    Compiler passes are registered differently is you are using the full
+    Compiler passes are registered differently if you are using the full
     stack framework, see :doc:`/cookbook/service_container/compiler_passes`
     for more details.
 
@@ -408,7 +408,7 @@ but getting an up to date configuration whilst developing your application::
 This could be further improved by only recompiling the container in debug
 mode when changes have been made to its configuration rather than on every
 request. This can be done by caching the resource files used to configure
-the container in the way describe in ":doc:`/components/config/caching`"
+the container in the way described in ":doc:`/components/config/caching`"
 in the config component documentation.
 
 You do not need to work out which files to cache as the container builder
diff --git a/components/dependency_injection/workflow.rst b/components/dependency_injection/workflow.rst
@@ -51,7 +51,7 @@ Bundle-level Configuration with Extensions
 
 By convention, each bundle contains an Extension class which is in the bundle's
 ``DependencyInjection`` directory. These are registered with the ``ContainerBuilder``
-when the kernel is booted. When the ``ContainerBuilder`` is :doc:`/compiled<components/dependency-injection/compilation>`,
+when the kernel is booted. When the ``ContainerBuilder`` is :doc:`compiled</components/dependency-injection/compilation>`,
 the application-level configuration relevant to the bundle's extension is
 passed to the Extension which also usually loads its own config file(s), typically from the bundle's
 ``Resources/config`` directory. The application-level config is usually processed
@@ -63,7 +63,7 @@ Compiler passes to allow Interaction between Bundles
 
 :ref:`Compiler passes<components-dependency-injection-compiler-passes>` are
 used to allow interaction between different bundles as they cannot affect
-each others configuration in the extension classes. One of the main uses is
+each other's configuration in the extension classes. One of the main uses is
 to process tagged services, allowing bundles to register services to picked
 up by other bundles, such as Monolog loggers, Twig extensions and Data Collectors
 for the Web Profiler. Compiler passes are usually placed in the bundle's
