Nov 17, 2017 · Nov 17, 2017
diff --git a/session/locale_sticky_session.rst b/session/locale_sticky_session.rst
 ==================================================

 Symfony stores the locale setting in the Request, which means that this setting
 is notautomtically saved ("sticky") across requests. But, you *can* store the locale
 is notautomatically 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
    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 beenset. 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.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -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 notautomtically saved ("sticky") across requests. But, you can store the locale
		is notautomatically saved ("sticky") across requests. But, you can store the locale
		in the session, so that it's used on subsequent requests.

		.. _creating-a-LocaleSubscriber:
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -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 beenset. 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.
Expand Down