Merge branch '2.8' into 3.3

* 2.8:
  parameter name typo
  [#8603] Rewording
  [BrowserKit] Updated Project URI of Goutte
  Changed the title of a Doctrine article to avoid confusion
  Reworded the introduction of event listeners article

Author: weaverryan

components/browser_kit.rst

@@ -233,4 +233,4 @@ Learn more
 * :doc:`/components/dom_crawler`
 
 .. _`Packagist`: https://packagist.org/packages/symfony/browser-kit
-.. _`Goutte`: https://github.com/fabpot/Goutte
+.. _`Goutte`: https://github.com/FriendsOfPHP/Goutte

doctrine/event_listeners_subscribers.rst

@@ -2,9 +2,10 @@
    single: Doctrine; Event listeners and subscribers
 
 .. _doctrine-event-config:
+.. _how-to-register-event-listeners-and-subscribers:
 
-How to Register Event Listeners and Subscribers
-===============================================
+Doctrine Event Listeners and Subscribers
+========================================
 
 Doctrine packages have a rich event system that fires events when almost anything
 happens inside the system. For you, this means that you can create arbitrary
@@ -188,15 +189,15 @@ For a full reference, see chapter `The Event System`_ in the Doctrine documentat
 Lazy loading for Event Listeners
 --------------------------------
 
-One subtle difference between listeners and subscribers is that Symfony can load 
+One subtle difference between listeners and subscribers is that Symfony can load
 entity listeners lazily. This means that your listener class will only be fetched
 from the service container (and thus be instantiated) once the event it is linked
 to actually fires.
 
-Lazy loading might give you a slight performance improvement when your listener 
-runs for events that rarely fire. Also, it can help you when you run into 
+Lazy loading might give you a slight performance improvement when your listener
+runs for events that rarely fire. Also, it can help you when you run into
 *circular dependency issues* that may occur when your listener service in turn
-depends on the DBAL connection. 
+depends on the DBAL connection.
 
 To mark a listener service as lazily loaded, just add the ``lazy`` attribute
 to the tag like so:

event_dispatcher.rst

@@ -9,10 +9,10 @@ During the execution of a Symfony application, lots of event notifications are
 triggered. Your application can listen to these notifications and respond to
 them by executing any piece of code.
 
-Internal events provided by Symfony itself are defined in the
-:class:`Symfony\\Component\\HttpKernel\\KernelEvents` class. Third-party bundles
-and libraries also trigger lots of events and your own application can trigger
-:doc:`custom events </components/event_dispatcher>`.
+Symfony triggers several :doc:`events related to the kernel </reference/events>`
+while processing the HTTP Request. Third-party bundles may also dispatch events, and
+you can even dispatch :doc:`custom events </components/event_dispatcher>` from your
+own code.
 
 All the examples shown in this article use the same ``KernelEvents::EXCEPTION``
 event for consistency purposes. In your own application, you can use any event

security/form_login.rst

@@ -34,7 +34,7 @@ several ways.
 Changing the default Page
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Define the ``default_security_target`` option to change the page where the user
+Define the ``default_target_path`` option to change the page where the user
 is redirected to if no previous page was stored in the session. The value can be
 a relative/absolute URL or a Symfony route name: