bencoder
diff --git a/‎components/http_foundation/session_php_bridge.rst
Lines changed: 10 additions & 10 deletions b/‎components/http_foundation/session_php_bridge.rst
Lines changed: 10 additions & 10 deletions
diff --git a/‎components/map.rst.inc
Lines changed: 1 addition & 0 deletions b/‎components/map.rst.inc
Lines changed: 1 addition & 0 deletions
diff --git a/‎cookbook/sessions/index.rst renamed to ‎cookbook/session/index.rst b/‎cookbook/sessions/index.rst renamed to ‎cookbook/session/index.rst
diff --git a/‎cookbook/session/php_bridge.rst
Lines changed: 36 additions & 0 deletions b/‎cookbook/session/php_bridge.rst
Lines changed: 36 additions & 0 deletions
diff --git a/‎cookbook/sessions/php_bridge.rst
Lines changed: 0 additions & 36 deletions b/‎cookbook/sessions/php_bridge.rst
Lines changed: 0 additions & 36 deletions
@@ -12,16 +12,16 @@ As stated elsewhere, Symfony Sessions are designed to replace the use of
 PHP's native ``session_*()`` functions and use of the ``$_SESSION``
 superglobal. Additionally, it is mandatory for Symfony to start the session.
 
-However when there really are circumstances where this is not possible, it is possible
-to use a special storage bridge
+However when there really are circumstances where this is not possible, you
+can use a special storage bridge
 :class:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\PhpBridgeSessionStorage`
 which is designed to allow Symfony to work with a session started outside of
 the Symfony Session framework. You are warned that things can interrupt this
-use case unless you are careful: for example legacy application erases ``$_SESSION``.
+use-case unless you are careful: for example the legacy application erases
+``$_SESSION``.
 
-Typical use of this might look as follows::
+A typical use of this might look like this::
 
-    <?php
     use Symfony\Component\HttpFoundation\Session\Session;
     use Symfony\Component\HttpFoundation\Session\Storage\PhpBridgeSessionStorage;
 
@@ -36,14 +36,14 @@ Typical use of this might look as follows::
     // symfony will now interface with the existing PHP session
     $session->start();
 
-This will allow you to start using the Symfony Session API and allow
-migration of your application to Symfony Sessions.
+This will allow you to start using the Symfony Session API and allow migration
+of your application to Symfony sessions.
 
 .. note::
 
-    Symfony Sessions store data like attributes in special 'Bags' which use a
-    key in the ``$_SESSION`` superglobal. This means that a Symfony Session
-    cannot access arbitary keys in ``$_SESSION`` that may be set by the legacy
+    Symfony sessions store data like attributes in special 'Bags' which use a
+    key in the ``$_SESSION`` superglobal. This means that a Symfony session
+    cannot access arbitrary keys in ``$_SESSION`` that may be set by the legacy
     application, although all the ``$_SESSION`` contents will be saved when
     the session is saved.
 
@@ -65,6 +65,7 @@
   * :doc:`/components/http_foundation/sessions`
   * :doc:`/components/http_foundation/session_configuration`
   * :doc:`/components/http_foundation/session_testing`
+  * :doc:`/components/http_foundation/session_php_bridge`
   * :doc:`/components/http_foundation/trusting_proxies`
 
 * :doc:`/components/http_kernel/index`
 
@@ -0,0 +1,36 @@
+.. index::
+   single: Sessions
+
+Bridge a legacy application with Symfony Sessions
+-------------------------------------------------
+
+.. versionadded:: 2.3
+    The ability to integrate with a legacy PHP session was added in Symfony 2.3.
+
+If you're integrating the Symfony full-stack Framework into a legacy application
+that starts the session with ``session_start()``, you may still be able to
+use Symfony's session management by using the PHP Bridge session.
+
+If the application has sets it's own PHP save handler, you can specify null
+for the ``handler_id``:
+
+.. code-block:: yaml
+
+    framework:
+        session:
+            storage_id: session.storage.php_bridge
+            handler_id: ~
+
+Otherwise, if the problem is simply that you cannot avoid the application
+starting the session with ``session_start()``, you can still make use of
+a Symfony based session save handler by specifying the save handler as in
+the example below:
+
+.. code-block:: yaml
+
+    framework:
+        session:
+            storage_id: session.storage.php_bridge
+            handler_id: session.handler.native_file
+
+For more details, see :doc:`/components/http_foundation/session_php_bridge`.