Skip to content

Commit c40a9d9

Browse files
committed
Fixed the last references to security.yml
1 parent b7c987c commit c40a9d9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

security/entity_provider.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Introduction
2424
Loading users via a Doctrine entity has 2 basic steps:
2525

2626
#. :ref:`Create your User entity <security-crete-user-entity>`
27-
#. :ref:`Configure security.yml to load from your entity <security-config-entity-provider>`
27+
#. :ref:`Configure security.yaml to load from your entity <security-config-entity-provider>`
2828

2929
Afterwards, you can learn more about :ref:`forbidding inactive users <security-advanced-user-interface>`,
3030
:ref:`using a custom query <authenticating-someone-with-a-custom-entity-provider>`

security/form_login_setup.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ Finally, create the template:
231231
The form can look like anything, but it usually follows some conventions:
232232

233233
* The ``<form>`` element sends a ``POST`` request to the ``login`` route, since
234-
that's what you configured under the ``form_login`` key in ``security.yml``;
234+
that's what you configured under the ``form_login`` key in ``security.yaml``;
235235
* The username field has the name ``_username`` and the password field has the
236236
name ``_password``.
237237

0 commit comments

Comments
 (0)