From 925267dbc84c260d21761cd15cde422ac6e5c23f Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Fri, 17 Nov 2017 10:33:59 +0100 Subject: [PATCH] Minor typos in session articles --- session/locale_sticky_session.rst | 2 +- session/php_bridge.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/session/locale_sticky_session.rst b/session/locale_sticky_session.rst index 4e89eb2ffc2..79c3723bf97 100644 --- a/session/locale_sticky_session.rst +++ b/session/locale_sticky_session.rst @@ -5,7 +5,7 @@ Making the Locale "Sticky" during a User's Session ================================================== Symfony stores the locale setting in the Request, which means that this setting -is not automtically saved ("sticky") across requests. But, you *can* store the locale +is not automatically saved ("sticky") across requests. But, you *can* store the locale in the session, so that it's used on subsequent requests. .. _creating-a-LocaleSubscriber: diff --git a/session/php_bridge.rst b/session/php_bridge.rst index f8c161f3ec6..3ebc74461ae 100644 --- a/session/php_bridge.rst +++ b/session/php_bridge.rst @@ -90,7 +90,7 @@ the example below: override this. Instead set ``handler_id: ~``. Note that a save handler cannot be changed once the session has been started. If the application starts the session before Symfony is initialized, the save handler will - have already been set. In this case, you will need ``handler_id: ~``. + have already been set. In this case, you will need ``handler_id: ~``. Only override the save handler if you are sure the legacy application can use the Symfony save handler without side effects and that the session has not been started before Symfony is initialized.