Minor fixes

Author: javiereguiluz

bundles/extension.rst

@@ -27,10 +27,11 @@ following conventions:
   ``AppExtension`` and the one for AcmeHelloBundle would be called
   ``AcmeHelloExtension``).
 
-The Extension class should implement the
+The Extension class must implement the
 :class:`Symfony\\Component\\DependencyInjection\\Extension\\ExtensionInterface`,
-but usually you would extend the
-:class:`Symfony\\Component\\DependencyInjection\\Extension\\Extension` class::
+but instead you should extend the
+:class:`Symfony\\Component\\DependencyInjection\\Extension\\Extension` class,
+which already implements the interface and provides some utilities::
 
     // src/Acme/HelloBundle/DependencyInjection/AcmeHelloExtension.php
     namespace Acme\HelloBundle\DependencyInjection;

components/stopwatch.rst

@@ -21,7 +21,7 @@ Alternatively, you can clone the `<https://github.com/symfony/stopwatch>`_ repos
 Usage
 -----
 
-The Stopwatch component provides an consistent way to measure execution
+The Stopwatch component provides a consistent way to measure execution
 time of certain parts of code so that you don't constantly have to parse
 microtime by yourself. Instead, use the simple
 :class:`Symfony\\Component\\Stopwatch\\Stopwatch` class::

create_framework/dependency_injection.rst

@@ -66,7 +66,7 @@ framework more configurable, but at the same time, it introduces a lot of
 issues:
 
 * We are not able to register custom listeners anymore as the dispatcher is
-  not available outside the Framework class (an workaround could be the
+  not available outside the Framework class (a workaround could be the
   adding of a ``Framework::getEventDispatcher()`` method);
 
 * We have lost the flexibility we had before; you cannot change the

create_framework/http_kernel_httpkernelinterface.rst

@@ -46,15 +46,15 @@ Update your framework so that it implements this interface::
         }
     }
 
-Even if this change looks not to complex, it brings us a lot! Let's talk about one of
+Even if this change looks not too complex, it brings us a lot! Let's talk about one of
 the most impressive one: transparent :doc:`HTTP caching </http_cache>` support.
 
 The ``HttpCache`` class implements a fully-featured reverse proxy, written in
 PHP; it implements ``HttpKernelInterface`` and wraps another
 ``HttpKernelInterface`` instance::
 
     // example.com/web/front.php
-    
+
     // ..
 
     $framework = new Simplex\Framework($dispatcher, $matcher, $controllerResolver, $argumentResolver);

http_cache.rst

@@ -77,7 +77,7 @@ but is a great way to start.
 
     For details on setting up Varnish, see :doc:`/http_cache/varnish`.
 
-Each application comes with a caching kernel (``AppCache``)that wraps the
+Each application comes with a caching kernel (``AppCache``) that wraps the
 default one (``AppKernel``). The caching Kernel *is* the reverse proxy.
 
 To enable caching, modify the code of your front controller. You can also make these