start translating "cookie"
Improved URL Rewrite settings in web.config to also catch favicon.ico
Merge pull request #582 from ravage84/favicon

Improved URL Rewrite settings in web.config to also catch favicon.ico
[fr] Follow #580 and add missing parts in form helper
[fr] Follow #581 and fix some grammar in routing.rst
[fr] Follow #582 and add missing parts in url-rewriting
fix composer link
[fr] Follow 61eecb5110adf8b3b56fa09642ce4c57102e4232 in advanced-installation

fix composer link
Update docs for containable.

Mention that it is not magic, and only manipulates existing
associations.
Update installation/deployment docs.

A very similar section was in 2 places, I think having it in the
advanced installation page makes more sense. Deployment should be just
about things you need to do for deployment.
[fr] Follow 7e6ac7b31583dd159a8e0918f9e80263a216282b

Update installation/deployment docs.
[fr] Follow 0682d8114b81e51c4418455d596b3e548732a2f8

Update docs for containable and fix typos
component's component does not receive callbacks

See: https://cakephp.lighthouseapp.com/projects/42648/tickets/3224-componentinitialize-in-not-triggered-for-components-included-into-other-components
Update saving-your-data.rst

The wording of the description for create() was very vague, misleading, complicated to understand.  The 2.3 API description of create() is much better, but still a bit lacking.  After tracing through the code to discover just what create() actually does and when and then doing some tests of my own, I've written some changes to the description which more accurately and effectively communicate what create() actually does.

1.) The previous description strongly hinted that create() actually had no effect on fields that "have already been set" prior to calling create() and only upon fields which "have already been set", which is not the case. Any data that is set prior to calling create() is actually overwritten completely by create().  I've updated the description to accurately describe the true effect upon Model::$data.

2.) I've added the fact that null may also be passed as the $data param, not just false.  This was in the API but not yet added here in the docs.

3.) I've added clarity to what happens when there are no database defaults AND no parameters passed for $data. In this case, Model::$data is set to an empty array.

4.) I've added clarity to what happens when false or null are passed for $data, regardless of there being any database defaults. In this case, Model::$data is set to an empty array.
Merge pull request #585 from pafuinlu/patch-2

Update to create() description in saving-your-data.rst
[fr] Follow #585

Update saving-your-data.rst
Merge pull request #584 from Schlaefer/patch-2

component's component does not receive callbacks
[fr] Follow #584

component's component does not receive callbacks and fix typos
Added example of using Controller::render() to render Plugin views
Merge pull request #586 from angelxmoreno/master

Added example of using Controller::render() to render Plugin views