Fixed broken use statements

Author: Nyholm

migration.rst

@@ -238,7 +238,7 @@ could look something like this::
     // public/index.php
     use App\Kernel;
     use App\LegacyBridge;
-    use Symfony\Component\Debug\Debug;
+    use Symfony\Component\ErrorHandler\Debug;
     use Symfony\Component\HttpFoundation\Request;
 
     require dirname(__DIR__).'/vendor/autoload.php';

reference/constraints/Traverse.rst

@@ -26,8 +26,8 @@ that all have constraints on their properties.
         // src/Entity/BookCollection.php
         namespace App\Entity;
 
-        use Doctrine\Collections\ArrayCollection;
-        use Doctrine\Collections\Collection
+        use Doctrine\Common\Collections\ArrayCollection;
+        use Doctrine\Common\Collections\Collection
         use Doctrine\ORM\Mapping as ORM;
         use Symfony\Component\Validator\Constraints as Assert;
 

routing.rst

@@ -2247,7 +2247,7 @@ session shouldn't be used when matching a request:
 
         // config/routes.php
         use App\Controller\MainController;
-        use Symfony\Bundle\FrameworkBundle\Routing\Loader\Configurator\RoutingConfigurator;
+        use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
         return function (RoutingConfigurator $routes) {
             $routes->add('homepage', '/')

translation.rst

@@ -307,10 +307,10 @@ parts of your application and mocking it in your tests.
 
 Instead of translating a string at the time of creation, you can use a
 "translatable object", which is an instance of the
-:class:`Symfony\\Component\\Translation\\TranslatableMessage` class. This object stores
+:class:`Symfony\\Component\\Translation\\Translatable` class. This object stores
 all the information needed to fully translate its contents when needed::
 
-    use Symfony\Component\Translation\TranslatableMessage;
+    use Symfony\Component\Translation\Translatable;
 
     // the first argument is required and it's the original message
     $message = new TranslatableMessage('Symfony is great!');