Fix wording and add missing wording

Author: gary houbre

controller/argument_value_resolver.rst

@@ -76,6 +76,7 @@ In the next example, you'll create a value resolver to inject the object that
 represents the current user whenever a controller method type-hints an argument
 with the ``User`` class::
 
+    // src/Controller/UserController.php
     namespace App\Controller;
 
     use App\Entity\User;

controller/error_pages.rst

@@ -208,7 +208,7 @@ JSON/XML/CSV/YAML encoders. When your application throws an exception, Symfony
 can output it in one of those formats. If you want to change the output
 contents, create a new Normalizer that supports the ``FlattenException`` input::
 
-    # src/App/Serializer/MyCustomProblemNormalizer.php
+    # src/Serializer/MyCustomProblemNormalizer.php
     namespace App\Serializer;
 
     use Symfony\Component\ErrorHandler\Exception\FlattenException;

controller/service.rst

@@ -26,6 +26,8 @@ a service like: ``App\Controller\HelloController::index``:
     .. code-block:: php-annotations
 
         // src/Controller/HelloController.php
+        namespace App\Controller;
+
         use Symfony\Component\Routing\Annotation\Route;
 
         class HelloController
@@ -87,6 +89,8 @@ which is a common practice when following the `ADR pattern`_
     .. code-block:: php-annotations
 
         // src/Controller/Hello.php
+        namespace App\Controller;
+
         use Symfony\Component\HttpFoundation\Response;
         use Symfony\Component\Routing\Annotation\Route;
 

controller/soap_web_service.rst

@@ -57,6 +57,7 @@ Finally, below is an example of a controller that is capable of handling a SOAP
 request. Because ``index()`` is accessible via ``/soap``, the WSDL document
 can be retrieved via ``/soap?wsdl``::
 
+    // src/Controller/HelloServiceController.php
     namespace App\Controller;
 
     use App\Service\HelloService;

controller/upload_file.rst

@@ -327,6 +327,8 @@ Then, define a service for this class:
 Now you're ready to use this service in the controller::
 
     // src/Controller/ProductController.php
+    namespace App\Controller;
+
     use App\Service\FileUploader;
     use Symfony\Component\HttpFoundation\Request;
 

deployment/fortrabbit.rst

@@ -9,4 +9,4 @@ Deploying to fortrabbit
 For details on deploying to fortrabbit, see their official documentation:
 `Install Symfony`_
 
-.. _`Install Symfony`: https://help.fortrabbit.com/install-symfony-3-uni
+.. _`Install Symfony`: https://help.fortrabbit.com/install-symfony-5-uni

doctrine/associations.rst

@@ -548,6 +548,7 @@ What about *removing* a ``Product`` from a ``Category``? The ``make:entity`` com
 also generated a ``removeProduct()`` method::
 
     // src/Entity/Category.php
+    namespace App\Entity;
 
     // ...
     class Category

doctrine/dbal.rst

@@ -44,6 +44,9 @@ if you *don't* want to use the Doctrine ORM.
 You can then access the Doctrine DBAL connection by autowiring the ``Connection``
 object::
 
+    // src/Controller/UserController.php
+    namespace App\Controller;
+
     use Doctrine\DBAL\Driver\Connection;
 
     class UserController extends AbstractController

doctrine/events.rst

@@ -56,6 +56,8 @@ define a callback for the ``prePersist`` Doctrine event:
     .. code-block:: php-annotations
 
         // src/Entity/Product.php
+        namespace App\Entity;
+
         use Doctrine\ORM\Mapping as ORM;
 
         // When using annotations, don't forget to add @ORM\HasLifecycleCallbacks()

doctrine/multiple_entity_managers.rst

@@ -230,6 +230,9 @@ When working with multiple entity managers to generate migrations:
 If you *do* omit the entity manager's name when asking for it,
 the default entity manager (i.e. ``default``) is returned::
 
+    // src/Controller/UserController.php
+    namespace App\Controller;
+
     // ...
 
     use Doctrine\ORM\EntityManagerInterface;
@@ -256,6 +259,9 @@ entity manager to persist and fetch its entities.
 
 The same applies to repository calls::
 
+    // src/Controller/UserController.php
+    namespace App\Controller;
+
     use AcmeStoreBundle\Entity\Customer;
     use AcmeStoreBundle\Entity\Product;
     // ...