Tweaks thanks for great reviews!

Author: weaverryan

controller/error_pages.rst

@@ -297,8 +297,8 @@ In that case, you might want to override one or both of the ``showAction()`` and
             // app/config/services.php
             use AppBundle\Controller\CustomExceptionController;
 
-            $$container->autowire(CustomExceptionController::class)
-                setArgument('$debug', '%kernel.debug%');
+            $container->autowire(CustomExceptionController::class)
+                ->setArgument('$debug', '%kernel.debug%');
 
 .. tip::
 

controller/soap_web_service.rst

@@ -51,7 +51,8 @@ In this case, the SOAP service will allow the client to call a method called
     }
 
 Next, make sure that your new class is registered as a service. If you use
-:doc:`autowiring </service_container/autowiring>` (enabled by default), this is easy:
+:doc:`autowiring </service_container/autowiring>` (enabled by default in the Symfony
+Standard Edition), this is easy:
 
 .. configuration-block::
 
@@ -60,10 +61,11 @@ Next, make sure that your new class is registered as a service. If you use
         # app/config/services.yml
         services:
             _defaults:
-                # be sure autowire is enabled
+                # ...
+                # be sure autowiring is enabled
                 autowire: true
 
-            # load services from the Service directory
+            # add Service/ to the list of directories to load services from
             AppBundle\:
                 resource: '../../src/AppBundle/{Service,Updates,Command,Form,EventSubscriber,Twig,Security}'
 
@@ -77,9 +79,9 @@ Next, make sure that your new class is registered as a service. If you use
                 http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <defaults autowire="true" autoconfigure="true" />
+                <defaults autowire="true" ... />
 
-                <!-- load services from the Service directory -->
+                <!-- add Service/ to the list of directories to load services from -->
                 <prototype namespace="AppBundle\" resource="../../src/AppBundle/{Service,Updates,Command,Form,EventSubscriber,Twig,Security}" />
             </services>
         </container>
@@ -93,7 +95,7 @@ Next, make sure that your new class is registered as a service. If you use
             ->setPublic(false);
 
 Below is an example of a controller that is capable of handling a SOAP
-request. BEcause ``indexAction()`` is accessible via ``/soap``, the WSDL document
+request. Because ``indexAction()`` is accessible via ``/soap``, the WSDL document
 can be retrieved via ``/soap?wsdl``::
 
     namespace AppBundle\Controller;

controller/upload_file.rst

@@ -221,7 +221,7 @@ Creating an Uploader Service
 To avoid logic in controllers, making them big, you can extract the upload
 logic to a separate service::
 
-    // src/AppBundle/Service\FileUploader.php
+    // src/AppBundle/Service/FileUploader.php
     namespace AppBundle\Service;
 
     use Symfony\Component\HttpFoundation\File\UploadedFile;
@@ -293,6 +293,7 @@ Then, define a service for this class:
 Now you're ready to use this service in the controller::
 
     // src/AppBundle/Controller/ProductController.php
+    use Symfony\Component\HttpFoundation\Request;
     use AppBundle\Service\FileUploader;
 
     // ...

doctrine/associations.rst

@@ -369,7 +369,7 @@ following method to the ``ProductRepository`` class::
     // src/AppBundle/Repository/ProductRepository.php
     use Doctrine\ORM\EntityManagerInterface;
 
-    public function findOneByIdJoinedToCategory($productId, EntityManagerInterface $em)
+    public function findOneByIdJoinedToCategory($productId)
     {
         $query = $em->createQuery(
             'SELECT p, c FROM AppBundle:Product p

doctrine/event_listeners_subscribers.rst

@@ -51,7 +51,7 @@ managers that use this connection.
         <container xmlns="http://symfony.com/schema/dic/services"
             xmlns:doctrine="http://symfony.com/schema/dic/doctrine">
             <services>
-                <!-- ... --
+                <!-- ... -->
 
                 <service id="AppBundle\EventListener\SearchIndexer">
                     <tag name="doctrine.event_listener" event="postPersist" />

doctrine/pdo_session_storage.rst

@@ -110,10 +110,12 @@ a second array argument to ``PdoSessionHandler``:
         use Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler;
         // ...
 
-        $container->register(PdoSessionHandler::class)->setArguments(array(
-            'mysql:dbname=mydatabase',
-            array('db_table' => 'sessions', 'db_username' => 'myuser', 'db_password' => 'mypassword')
-        ));
+        $container->register(PdoSessionHandler::class)
+            ->setArguments(array(
+                'mysql:dbname=mydatabase',
+                array('db_table' => 'sessions', 'db_username' => 'myuser', 'db_password' => 'mypassword')
+            ))
+        ;
 
 These are parameters that you must configure:
 
@@ -170,10 +172,12 @@ of your project's data, you can use the connection settings from the
     .. code-block:: php
 
         // ...
-        $container->register(PdoSessionHandler::class)->setArguments(array(
-            'mysql:host=%database_host%;port=%database_port%;dbname=%database_name%',
-            array('db_username' => '%database_user%', 'db_password' => '%database_password%')
-        ));
+        $container->register(PdoSessionHandler::class)
+            ->setArguments(array(
+                'mysql:host=%database_host%;port=%database_port%;dbname=%database_name%',
+                array('db_username' => '%database_user%', 'db_password' => '%database_password%')
+            ))
+        ;
 
 .. _example-sql-statements:
 

event_dispatcher.rst

@@ -184,7 +184,7 @@ the ``EventSubscriber`` directory. Symfony takes care of the rest.
     If your methods are *not* called when an exception is thrown, double-check that
     you're :ref:`loading services <service-container-services-load-example>` from
     the ``EventSubscriber`` directory and have :ref:`autoconfigure <services-autoconfigure>`
-    enabled. You can also manually tag with ``kernel.event_subscriber``.
+    enabled. You can also manually add the ``kernel.event_subscriber`` tag.
 
 Request Events, Checking Types
 ------------------------------