Merge branch '4.4'

* 4.4:
  There is no handler file in storage
  [PHPUnit Bridge] Minor tweaks related to polyfills

Author: OskarStark

components/phpunit_bridge.rst

@@ -389,7 +389,7 @@ Polyfills for the Unavailable Methods
 
 When using the ``simple-phpunit`` script, PHPUnit Bridge injects polyfills for
 most methods of the ``TestCase`` and ``Assert`` classes (e.g. ``expectException()``,
-``expectExcpetionMessage()``, ``assertContainsEquals``, etc.). This allows writing
+``expectExceptionMessage()``, ``assertContainsEquals()``, etc.). This allows writing
 test cases using the latest best practices while still remaining compatible with
 older PHPUnit versions.
 
@@ -413,18 +413,18 @@ call to the ``doSetUp()``, ``doTearDown()``, ``doSetUpBeforeClass()`` and
 
     class MyTest extends TestCase
     {
+        // when using the SetUpTearDownTrait, methods like doSetup() can
+        // be defined with and without the 'void' return type, as you wish
         use SetUpTearDownTrait;
 
-        private $state;
-
         private function doSetup()
         {
-            $this->state = 'demo';
+            // ...
         }
 
         protected function doSetup(): void
         {
-            // visibility and return type-hint of method is free
+            // ...
         }
     }
 

doctrine/pdo_session_storage.rst

@@ -184,7 +184,7 @@ Preparing the Database to Store Sessions
 
 Before storing sessions in the database, you must create the table that stores
 the information. The session handler provides a method called
-:method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\Handler::createTable`
+:method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\Handler\\PdoSessionHandler::createTable`
 to set up this table for you according to the database engine used::
 
     try {