Merge branch '2.4'

Conflicts:
	book/routing.rst
	book/security.rst
	changelog.rst
	components/config/definition.rst
	components/dependency_injection/compilation.rst
	components/finder.rst
	components/http_foundation/introduction.rst
	components/process.rst
	components/property_access/introduction.rst
	components/stopwatch.rst
	cookbook/console/sending_emails.rst
	cookbook/templating/render_without_controller.rst
	reference/constraints/CardScheme.rst
	reference/constraints/Luhn.rst
	reference/twig_reference.rst

Author: weaverryan

book/forms.rst

@@ -232,10 +232,10 @@ controller::
     }
 
 .. versionadded:: 2.3
-    The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method was
-    added in Symfony 2.3. Previously, the ``$request`` was passed to the
-    ``submit`` method - a strategy which is deprecated and will be removed
-    in Symfony 3.0. For details on that method, see :ref:`cookbook-form-submit-request`.
+    The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method
+    was introduced in Symfony 2.3. Previously, the ``$request`` was passed
+    to the ``submit`` method - a strategy which is deprecated and will be
+    removed in Symfony 3.0. For details on that method, see :ref:`cookbook-form-submit-request`.
 
 This controller follows a common pattern for handling forms, and has three
 possible paths:

book/page_creation.rst

@@ -1061,5 +1061,5 @@ to rapidly develop applications.
 .. _`Twig`: http://twig.sensiolabs.org
 .. _`third-party bundles`: http://knpbundles.com
 .. _`Symfony Standard Edition`: http://symfony.com/download
-.. _`Apache's DirectoryIndex documentation`: http://httpd.apache.org/docs/2.0/mod/mod_dir.html
+.. _`Apache's DirectoryIndex documentation`: http://httpd.apache.org/docs/current/mod/mod_dir.html
 .. _`Nginx HttpCoreModule location documentation`: http://wiki.nginx.org/HttpCoreModule#location

book/testing.rst

@@ -415,8 +415,9 @@ Accessing internal Objects
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. versionadded:: 2.3
-    The ``getInternalRequest()`` and ``getInternalResponse()`` method were
-    added in Symfony 2.3.
+    The :method:`Symfony\\Component\\BrowserKit\\Client::getInternalRequest`
+    and :method:`Symfony\\Component\\BrowserKit\\Client::getInternalResponse`
+    methods were introduced in Symfony 2.3.
 
 If you use the client to test your application, you might want to access the
 client's internal objects::

changelog.rst

@@ -206,8 +206,9 @@ New Documentation
 Fixed Documentation
 ~~~~~~~~~~~~~~~~~~~
 
-- `adcbb5d <https://github.com/symfony/symfony-docs/commit/adcbb5de6c3b8d6ba59e619315ef13fe45318494>`_ #3615 Fixes to cookbook/doctrine/registration_form.rst (Crushnaut)
 - `5c4336a <https://github.com/symfony/symfony-docs/commit/5c4336a325ec98bc0eb7ef35baf86bcb9628e490>`_ #3570 Callback: [Validator, validate] expects validate to be static (nixilla)
+- `5c367b4 <https://github.com/symfony/symfony-docs/commit/5c367b4dfa5c3adc8993702b1ae8f686c74419c8>`_ #3517 Fixed OptionsResolver component docs (WouterJ)
+- `adcbb5d <https://github.com/symfony/symfony-docs/commit/adcbb5de6c3b8d6ba59e619315ef13fe45318494>`_ #3615 Fixes to cookbook/doctrine/registration_form.rst (Crushnaut)
 - `a21fb26 <https://github.com/symfony/symfony-docs/commit/a21fb260978eaa27b1cb94fccb0bd0af71b6df7f>`_ #3559 Remove reference to copying parameters.yml from Git cookbook (pwaring)
 - `de71a51 <https://github.com/symfony/symfony-docs/commit/de71a5143f6d30fff7e890cea250d047a63916d2>`_ #3551 [Cookbook][Dynamic Form Modification] Fix sample code (rybakit)
 - `143db2f <https://github.com/symfony/symfony-docs/commit/143db2f75caa9ef6d7e1c230d0ac9d59c17fde5f>`_ #3550 Update introduction.rst (taavit)

components/config/caching.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Config; Caching based on resources
 
-Caching based on resources
+Caching Based on Resources
 ==========================
 
 When all configuration resources are loaded, you may want to process the configuration

components/config/definition.rst

@@ -1,10 +1,10 @@
 .. index::
    single: Config; Defining and processing configuration values
 
-Defining and processing configuration values
+Defining and Processing Configuration Values
 ============================================
 
-Validating configuration values
+Validating Configuration Values
 -------------------------------
 
 After loading configuration values from all kinds of resources, the values
@@ -38,7 +38,7 @@ they are when first encountered. Also, some keys are only available when
 another key has a specific value (in the sample configuration above: the
 ``memory`` key only makes sense when the ``driver`` is ``sqlite``).
 
-Defining a hierarchy of configuration values using the TreeBuilder
+Defining a Hierarchy of Configuration Values Using the TreeBuilder
 ------------------------------------------------------------------
 
 All the rules concerning configuration values can be defined using the
@@ -66,10 +66,10 @@ should be returned from a custom ``Configuration`` class which implements the
         }
     }
 
-Adding node definitions to the tree
+Adding Node Definitions to the Tree
 -----------------------------------
 
-Variable nodes
+Variable Nodes
 ~~~~~~~~~~~~~~
 
 A tree contains node definitions which can be laid out in a semantic way.
@@ -91,7 +91,7 @@ The root node itself is an array node, and has children, like the boolean
 node ``auto_connect`` and the scalar node ``default_connection``. In general:
 after defining a node, a call to ``end()`` takes you one step up in the hierarchy.
 
-Node type
+Node Type
 ~~~~~~~~~
 
 It is possible to validate the type of a provided value by using the appropriate
@@ -108,7 +108,7 @@ node definition. Node type are available for:
 and are created with ``node($name, $type)`` or their associated shortcut
 ``xxxxNode($name)`` method.
 
-Numeric node constraints
+Numeric Node Constraints
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 Numeric nodes (float and integer) provide two extra constraints -
@@ -130,7 +130,7 @@ allowing to validate the value::
         ->end()
     ;
 
-Enum nodes
+Enum Nodes
 ~~~~~~~~~~
 
 Enum nodes provide a constraint to match the given input against a set of
@@ -146,7 +146,7 @@ values::
 
 This will restrict the ``gender`` option to be either ``male`` or ``female``.
 
-Array nodes
+Array Nodes
 ~~~~~~~~~~~
 
 It is possible to add a deeper level to the hierarchy, by adding an array
@@ -187,7 +187,7 @@ inside the current node. According to the prototype definition in the example
 above, it is possible to have multiple connection arrays (containing a ``driver``,
 ``host``, etc.).
 
-Array node options
+Array Node Options
 ~~~~~~~~~~~~~~~~~~
 
 Before defining the children of an array node, you can provide options like:
@@ -230,7 +230,7 @@ In XML, each ``parameters`` node would have a ``name`` attribute (along with
 the final array. The ``useAttributeAsKey`` is useful for normalizing how
 arrays are specified between different formats like XML and YAML.
 
-Default and required values
+Default and required Values
 ---------------------------
 
 For all node types, it is possible to define default values and replacement
@@ -307,7 +307,7 @@ you can take advantage of the shortcut
 The ``canBeDisabled`` method looks about the same except that the section
 would be enabled by default.
 
-Merging options
+Merging Options
 ---------------
 
 Extra options concerning the merge process may be provided. For arrays:
@@ -321,7 +321,7 @@ For all nodes:
 ``cannotBeOverwritten()``
     don’t let other configuration arrays overwrite an existing value for this node
 
-Appending sections
+Appending Sections
 ------------------
 
 If you have a complex configuration to validate then the tree can grow to
@@ -493,7 +493,7 @@ By changing a string value into an associative array with ``name`` as the key::
         ->end()
     ;
 
-Validation rules
+Validation Rules
 ----------------
 
 More advanced validation rules can be provided using the
@@ -539,7 +539,7 @@ Usually, "then" is a closure. Its return value will be used as a new value
 for the node, instead
 of the node's original value.
 
-Processing configuration values
+Processing Configuration Values
 -------------------------------
 
 The :class:`Symfony\\Component\\Config\\Definition\\Processor` uses the tree

components/config/resources.rst

@@ -1,10 +1,10 @@
 .. index::
    single: Config; Loading resources
 
-Loading resources
+Loading Resources
 =================
 
-Locating resources
+Locating Resources
 ------------------
 
 Loading the configuration normally starts with a search for resources – in
@@ -24,7 +24,7 @@ look in this directory first. The third argument indicates whether or not the
 locator should return the first file it has found, or an array containing
 all matches.
 
-Resource loaders
+Resource Loaders
 ----------------
 
 For each type of resource (YAML, XML, annotation, etc.) a loader must be defined.
@@ -57,7 +57,7 @@ class, which allows for recursively importing other resources::
         }
     }
 
-Finding the right loader
+Finding the right Loader
 ------------------------
 
 The :class:`Symfony\\Component\\Config\\Loader\\LoaderResolver` receives as

components/console/events.rst

@@ -5,7 +5,7 @@ Using Events
 ============
 
 .. versionadded:: 2.3
-    Console events were added in Symfony 2.3.
+    Console events were introduced in Symfony 2.3.
 
 The Application class of the Console component allows you to optionally hook
 into the lifecycle of a console application via events. Instead of reinventing
@@ -51,7 +51,7 @@ dispatched. Listeners receive a
         $application = $command->getApplication();
     });
 
-The ``ConsoleEvents::TERMINATE`` event
+The ``ConsoleEvents::TERMINATE`` Event
 --------------------------------------
 
 **Typical Purposes**: To perform some cleanup actions after the command has
@@ -89,7 +89,7 @@ Listeners receive a
     It is then dispatched just before the ``ConsoleEvents::EXCEPTION`` event.
     The exit code received in this case is the exception code.
 
-The ``ConsoleEvents::EXCEPTION`` event
+The ``ConsoleEvents::EXCEPTION`` Event
 --------------------------------------
 
 **Typical Purposes**: Handle exceptions thrown during the execution of a

components/console/helpers/dialoghelper.rst

@@ -23,7 +23,7 @@ All the methods inside the Dialog Helper have an
 argument, the question as the second argument and the default value as the last
 argument.
 
-Asking the User for confirmation
+Asking the User for Confirmation
 --------------------------------
 
 Suppose you want to confirm an action before actually executing it. Add
@@ -172,7 +172,7 @@ You can also ask and validate a hidden response::
 If you want to allow the response to be visible if it cannot be hidden for
 some reason, pass true as the fifth argument.
 
-Let the user choose from a list of Answers
+Let the User Choose from a List of Answers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you have a predefined set of answers the user can choose from, you
@@ -240,7 +240,7 @@ this set the seventh argument to ``true``::
 Now, when the user enters ``1,2``, the result will be:
 ``You have just selected: blue, yellow``.
 
-Testing a Command which expects input
+Testing a Command which Expects Input
 -------------------------------------
 
 If you want to write a unit test for a command which expects some kind of input

components/console/introduction.rst

@@ -472,7 +472,7 @@ method::
     You can also test a whole console application by using
     :class:`Symfony\\Component\\Console\\Tester\\ApplicationTester`.
 
-Calling an existing Command
+Calling an Existing Command
 ---------------------------
 
 If a command depends on another one being run before it, instead of asking the