Corrected name of listener registry

3.0/usage/dispatcher-setup.md

@@ -19,7 +19,7 @@ $dispatcher = new EventDispatcher();
 ## Supplying a `Psr\EventDispatcher\ListenerProviderInterface`
 
 By default, the event dispatcher will create its own internal listener
-collection, which implements the listener interface as defined by PSR-14.
+registry, which implements the listener interface as defined by PSR-14.
 
 If needed, you can supply an alternate PSR-14 implementation in the constructor. 
 

3.0/usage/subscribing-to-events.md

@@ -9,23 +9,23 @@ The `League\Event\ListenerRegistry` (interface) allows you to subscribe to
 events. There are two implementations of this interface:
 
 1. `League\Event\EventDispatcher`
-2. `League\Event\PrioritizedListenerCollection`
+2. `League\Event\PrioritizedListenerRegistry`
 
 This means you can subscribe to events with the event dispatcher directly, or
-subscribe to the internal listener collection:
+subscribe to the internal listener registry:
 
 ```php
 use League\Event\EventDispatcher;
-use League\Event\PrioritizedListenerCollection;
+use League\Event\PrioritizedListenerRegistry;
 
-$listenerProvider = new PrioritizedListenerCollection();
+$listenerRegistry = new PrioritizedListenerRegistry();
 $dispatcher = new EventDispatcher($listenerProvider);
 
 // Subscribe with the dispatcher
-$listenerProvider->subscribeTo($eventIdentifier, $listener);
+$dispatcher->subscribeTo($eventIdentifier, $listener);
 
-// Subscribe with the listener provider
-$listenerProvider->subscribeTo($eventIdentifier, $listener);
+// Subscribe with the listener registry
+$listenerRegistry->subscribeTo($eventIdentifier, $listener);
 ```
 
 ## Subscribing parameters