Tweaks thanks to Javier's reviews

Author: weaverryan

bundles/best_practices.rst

@@ -386,7 +386,7 @@ For example, AcmeBlogBundle services must be prefixed with ``acme_blog``.
 In addition, services not meant to be used by the application directly, should
 be :ref:`defined as private <container-private-services>`. For public services,
 :ref:`aliases should be created <service-autowiring-alias>` from the interface/class
-to the service id. For example, in MonlogBundle, an alias is created from
+to the service id. For example, in MonologBundle, an alias is created from
 ``Psr\Log\LoggerInterface`` to ``logger`` so that the ``LoggerInterface`` type-hint
 can be used for autowiring.
 

console/commands_as_services.rst

@@ -6,12 +6,12 @@ How to Define Commands as Services
 
 If you're using the :ref:`default services.yml configuration <service-container-services-load-example>`,
 your command classes are already registered as services. Great! This is the recommended
-setup, but it's not required. Symfony also looks in the ``Command`` directory of
+setup, but it's not required. Symfony also looks in the ``Command/`` directory of
 each bundle and automatically registers those classes as commands.
 
 .. note::
 
-    You can also manually register your command as a service by configure the service
+    You can also manually register your command as a service by configuring the service
     and :doc:`tagging it </service_container/tags>` with ``console.command``.
 
 In either case, if your class extends :class:`Symfony\\Bundle\\FrameworkBundle\\Command\\ContainerAwareCommand`,
@@ -45,7 +45,7 @@ For example, suppose you want to log something from within your command::
         {
             $this
                 ->setName('app:sunshine')
-                ->setDescription('Hello PhpStorm');
+                ->setDescription('Good morning!');
         }
 
         protected function execute(InputInterface $input, OutputInterface $output)

controller/service.rst

@@ -7,7 +7,7 @@ How to Define Controllers as Services
 In Symfony, a controller does *not* need to be registered as a service. But if you're
 using the :ref:`default services.yml configuration <service-container-services-load-example>`,
 your controllers *are* already registered as services. This means you can use dependency
-injection line any other normal service.
+injection like any other normal service.
 
 Referencing your Service from Routing
 -------------------------------------
@@ -88,8 +88,8 @@ When using a controller defined as a service, you can still extend any of the
 use their shortcuts. But, you don't need to! You can choose to extend *nothing*,
 and use dependency injection to access difference services.
 
-The base `Controller class source code`_ is a great way to see how to performance
-simple tasks. For example, ``$this->render()`` is usually used to render a Twig
+The base `Controller class source code`_ is a great way to see how to accomplish
+common tasks. For example, ``$this->render()`` is usually used to render a Twig
 template and return a Response. But, you can also do this directly:
 
 In a controller that's defined as a service, you can instead inject the ``templating``
@@ -112,7 +112,7 @@ service and use it directly::
         public function indexAction($name)
         {
             $content = $this->twig->renderResponse(
-                'hellp/index.html.twig',
+                'hello/index.html.twig',
                 array('name' => $name)
             );
 
@@ -130,7 +130,7 @@ The best way to see how to replace base ``Controller`` convenience methods is to
 look at the `ControllerTrait`_ that holds its logic.
 
 If you want to know what type-hints to use for each service, see the
-``getSubscribedEvents`` in `AbstractController`_.
+``getSubscribedEvents()`` method in `AbstractController`_.
 
 .. _`Controller class source code`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/ControllerTrait.php
 .. _`base Controller class`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/ControllerTrait.php

service_container/service_decoration.rst

@@ -48,7 +48,7 @@ the original service is lost:
         $container->register('app.mailer', DecoratingMailer::class);
 
 Most of the time, that's exactly what you want to do. But sometimes,
-you might want to decorate the old service instead: keeping the old service so
+you might want to decorate the old service instead and keep the old service so
 that you can reference it:
 
 .. configuration-block::