Merge branch '2.3'

Author: weaverryan

book/page_creation.rst

@@ -52,7 +52,7 @@ front controller that can be used with any environment.)
 When the front controller initializes the kernel, it provides two parameters:
 the environment, and also whether the kernel should run in debug mode.
 To make your application respond faster, Symfony2 maintains a cache under the
-``app/cache/`` directory. When in debug mode is enabled (such as ``app_dev.php``
+``app/cache/`` directory. When debug mode is enabled (such as ``app_dev.php``
 does by default), this cache is flushed automatically whenever you make changes
 to any code or configuration. When running in debug mode, Symfony2 runs
 slower, but your changes are reflected without having to manually clear the

components/dependency_injection/definitions.rst

@@ -66,7 +66,7 @@ To get an array of the constructor arguments for a definition you can use::
 or to get a single argument by its position::
 
     $definition->getArgument($index);
-    //e.g. $definition->getArgument(0) for the first argument
+    // e.g. $definition->getArgument(0) for the first argument
 
 You can add a new argument to the end of the arguments array using::
 

components/filesystem.rst

@@ -178,9 +178,9 @@ Rename
 :method:`Symfony\\Component\\Filesystem\\Filesystem::rename` is used to rename
 files and directories::
 
-    //rename a file
+    // rename a file
     $fs->rename('/tmp/processed_video.ogg', '/path/to/store/video_647.ogg');
-    //rename a directory
+    // rename a directory
     $fs->rename('/tmp/files', '/path/to/store/files');
 
 symlink

components/form/introduction.rst

@@ -146,14 +146,14 @@ component offers a rich integration.
 
 To use the integration, you'll need the ``TwigBridge``, which provides integration
 between Twig and several Symfony2 components. If you're using Composer, you
-could install the latest 2.1 version by adding the following ``require``
+could install the latest 2.3 version by adding the following ``require``
 line to your ``composer.json`` file:
 
 .. code-block:: json
 
     {
         "require": {
-            "symfony/twig-bridge": "2.1.*"
+            "symfony/twig-bridge": "2.3.*"
         }
     }
 
@@ -222,15 +222,15 @@ via your own Twig extension.
 
 To use the built-in integration, be sure that your project has Symfony's
 ``Translation`` and :doc:`Config </components/config/introduction>` components
-installed. If you're using Composer, you could get the latest 2.1 version
+installed. If you're using Composer, you could get the latest 2.3 version
 of each of these by adding the following to your ``composer.json`` file:
 
 .. code-block:: json
 
     {
         "require": {
-            "symfony/translation": "2.1.*",
-            "symfony/config": "2.1.*"
+            "symfony/translation": "2.3.*",
+            "symfony/config": "2.3.*"
         }
     }
 
@@ -274,13 +274,13 @@ array or object) and pass it through your own validation system.
 
 To use the integration with Symfony's Validator component, first make sure
 it's installed in your application. If you're using Composer and want to
-install the latest 2.1 version, add this to your ``composer.json``:
+install the latest 2.3 version, add this to your ``composer.json``:
 
 .. code-block:: json
 
     {
         "require": {
-            "symfony/validator": "2.1.*"
+            "symfony/validator": "2.3.*"
         }
     }
 
@@ -557,7 +557,7 @@ If the request is a POST, process the submitted data (via ``bind``). Then:
     to ``bind``::
 
         if (isset($_POST[$form->getName()])) {
-            $form->bind($_POST[$form->getName())
+            $form->bind($_POST[$form->getName()]);
 
             // ...
         }

components/http_foundation/session_configuration.rst

@@ -249,12 +249,17 @@ using the `Native*SessionHandler` classes, while
 :class:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\Handler\\SessionHandlerProxy`
 will be used to wrap any custom save handlers, that implement :phpclass:`SessionHandlerInterface`.
 
-Under PHP 5.4 and above, all session handlers implement :phpclass:`SessionHandlerInterface`
+From PHP 5.4 and above, all session handlers implement :phpclass:`SessionHandlerInterface`
 including `Native*SessionHandler` classes which inherit from :phpclass:`SessionHandler`.
 
 The proxy mechanism allows you to get more deeply involved in session save handler
 classes. A proxy for example could be used to encrypt any session transaction
 without knowledge of the specific save handler.
 
+.. note::
+
+    Before PHP 5.4, you can only proxy user-land save handlers but not 
+    native PHP save handlers.
+
 .. _`php.net/session.customhandler`: http://php.net/session.customhandler
 .. _`php.net/session.configuration`: http://php.net/session.configuration

cookbook/configuration/apache_router.rst

@@ -129,11 +129,11 @@ to ``ApacheRequest`` in ``web/app.php``::
 
     require_once __DIR__.'/../app/bootstrap.php.cache';
     require_once __DIR__.'/../app/AppKernel.php';
-    //require_once __DIR__.'/../app/AppCache.php';
+    // require_once __DIR__.'/../app/AppCache.php';
 
     use Symfony\Component\HttpFoundation\ApacheRequest;
 
     $kernel = new AppKernel('prod', false);
     $kernel->loadClassCache();
-    //$kernel = new AppCache($kernel);
+    // $kernel = new AppCache($kernel);
     $kernel->handle(ApacheRequest::createFromGlobals())->send();

cookbook/security/acl.rst

@@ -9,7 +9,7 @@ cannot only be based on the person (``Token``) who is requesting access, but
 also involve a domain object that access is being requested for. This is where
 the ACL system comes in.
 
-.. sidebar:: Alternatives to ACLS
+.. sidebar:: Alternatives to ACLs
 
     Using ACL's isn't trivial, and for simpler use cases, it may be overkill.
     If your permission logic could be described by just writing some code (e.g.

cookbook/security/entity_provider.rst

@@ -649,7 +649,7 @@ this:
 
 .. code-block:: text
 
-    $ mysql> select * from acme_users;
+    $ mysql> select * from acme_role;
     +----+-------+------------+
     | id | name  | role       |
     +----+-------+------------+

quick_tour/the_controller.rst

@@ -131,7 +131,7 @@ from any controller::
     $foo = $session->get('foo');
 
     // use a default value if the key doesn't exist
-    $filters = $session->set('filters', array());
+    $filters = $session->get('filters', array());
 
 You can also store small messages that will only be available for the very
 next request::