@@ -201,7 +201,8 @@ see :ref:`controller-string-syntax`.
201201
202202..tip ::
203203
204- You can learn much more about the routing system in the:doc: `Routing chapter </book/routing >`.
204+ You can learn much more about the routing system in the
205+ :doc: `Routing chapter </book/routing >`.
205206
206207..index ::
207208 single: Controller; Controller arguments
@@ -225,15 +226,15 @@ to that method::
225226 {
226227 public function indexAction($name)
227228 {
228- // ...
229+ // ...
229230 }
230231 }
231232
232233The controller has a single argument, ``$name ``, which corresponds to the
233234``{name} `` parameter from the matched route (``ryan `` in the example). In
234235fact, when executing your controller, Symfony matches each argument of
235- the controller with a parameter from the matched route. Take the following
236- example:
236+ the controller with a parameter from the matched route by its name . Take the
237+ following example:
237238
238239..configuration-block ::
239240
@@ -421,15 +422,17 @@ Common Controller Tasks
421422Though a controller can do virtually anything, most controllers will perform
422423the same basic tasks over and over again. These tasks, such as redirecting,
423424forwarding, rendering templates and accessing core services, are very easy
424- to manage in Symfony.
425+ to manage in Symfony when you're extending the base `` Controller `` class .
425426
426427..index ::
427428 single: Controller; Redirecting
428429
429430Redirecting
430431~~~~~~~~~~~
431432
432- If you want to redirect the user to another page, use the ``redirect() `` method::
433+ If you want to redirect the user to another page, use the
434+ :method: `Symfony\\ Bundle\\ FrameworkBundle\\ Controller\\ Controller::redirect `
435+ method::
433436
434437 public function indexAction()
435438 {