Oct 26, 2018 · Oct 25, 2018
diff --git a/controller.rst b/controller.rst
 .. tip::

    You can extend either ``Controller`` or ``AbstractController``. The difference
    is that when you extend ``AbstractController``, you can't access services directly
    via ``$this->get()`` or ``$this->container->get()``. This forces you to write
    more robust code to access services. But if you *do* need direct access to the
    container, using ``Controller`` is fine.
    is that when you extend ``AbstractController``, you can't access to your services
    via ``$this->get()`` or ``$this->container->get()``, only to a set of common
    Symfony services. This forces you to write more robust code to access services.

    Moreover, in Symfony 4.2 ``Controller`` was deprecated in favor of
    ``AbstractController``, so using the latter will make your apps future-proof.

 .. versionadded:: 3.3
    The ``AbstractController`` class was added in Symfony 3.3.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -147,10 +147,12 @@ and many others that you'll learn about next.
		.. tip::

		You can extend either ``Controller`` or ``AbstractController``. The difference
		is that when you extend ``AbstractController``, you can't access services directly
		via ``$this->get()`` or ``$this->container->get()``. This forces you to write
		more robust code to access services. But if you do need direct access to the
		container, using ``Controller`` is fine.
		is that when you extend ``AbstractController``, you can't access to your services
		via ``$this->get()`` or ``$this->container->get()``, only to a set of common
		Symfony services. This forces you to write more robust code to access services.

		Moreover, in Symfony 4.2 ``Controller`` was deprecated in favor of
		``AbstractController``, so using the latter will make your apps future-proof.

		.. versionadded:: 3.3
		The ``AbstractController`` class was added in Symfony 3.3.
Expand Down