minor symfony#9282 Controller naming habits (Guikingone, javiereguiluz)

This PR was merged into the 4.0 branch.

Discussion
----------

Controller naming habits

As Symfony isn't an `MVC` framework but a `Request/Response` one (see symfony#8153 (comment)), the name of the class which handles the Request isn't forced to contain `Controller`, it's probably more a common usage than a need to make Symfony works.

Commits
-------

5b29f5b Minor reword
2b61e3b suggest(Controller): suggestion about naming habits

Author: javiereguiluz

controller.rst

@@ -58,8 +58,8 @@ This controller is pretty straightforward:
   the ``use`` keyword imports the ``Response`` class, which the controller
   must return.
 
-* *line 7*: The class can technically be called anything - but should end in the
-  word ``Controller``
+* *line 7*: The class can technically be called anything, but it's suffixed
+  with ``Controller`` by convention.
 
 * *line 12*: The action method is allowed to have a ``$max`` argument thanks to the
   ``{max}`` :doc:`wildcard in the route </routing>`.