Oct 22, 2020 · Aug 28, 2020
diff --git a/configuration/override_dir_structure.rst b/configuration/override_dir_structure.rst
 -----------------------------------

 If your translation files are not stored in the default ``translations/``
 directory, use the :ref:`framework.translator.paths <reference-translator-paths>`
 configuration option to define your own translations directory (or directories):
 directory, use the :ref:`framework.translator.default_path <reference-translator-default_path>`
 configuration option to define your own translations directory (use :ref:`framework.translator.paths <reference-translator-paths>` for multiple directories):

 .. configuration-block::

        framework:
            translator:
                # ...
 paths: ["%kernel.project_dir%/i18n"]
 default_path:"%kernel.project_dir%/i18n"

    .. code-block:: xml


            <framework:config>
                <framework:translator>
                    <framework:path>%kernel.project_dir%/i18n</framework:path>
                    <framework:default-path>%kernel.project_dir%/i18n</framework:default-path>
                </framework:translator>
            </framework:config>

        // config/packages/translation.php
        $container->loadFromExtension('framework', [
            'translator' => [
                'paths' => [
                    '%kernel.project_dir%/i18n',
                ],
                'default_path' => '%kernel.project_dir%/i18n',
            ],
        ]);

 -----------------------------

 If you need to rename or move your ``public/`` directory, the only thing you
 need to guarantee is that the path to the ``var/`` directory is still correct in
 need to guarantee is that the path to the ``vendor/`` directory is still correct in
 your ``index.php`` front controller. If you renamed the directory, you're fine.
 But if you moved it in some way, you may need to modify these paths inside those
 files::
Original file line number	Diff line number	Diff line change
Expand Up		@@ -141,8 +141,8 @@ Override the Translations Directory
		-----------------------------------

		If your translation files are not stored in the default ``translations/``
		directory, use the :ref:`framework.translator.paths <reference-translator-paths>`
		configuration option to define your own translations directory (or directories):
		directory, use the :ref:`framework.translator.default_path <reference-translator-default_path>`
		configuration option to define your own translations directory (use :ref:`framework.translator.paths <reference-translator-paths>` for multiple directories):

		.. configuration-block::

Expand All		@@ -152,7 +152,7 @@ configuration option to define your own translations directory (or directories):
		framework:
		translator:
		# ...
		paths: ["%kernel.project_dir%/i18n"]
		default_path:"%kernel.project_dir%/i18n"

		.. code-block:: xml

Expand All		@@ -168,7 +168,7 @@ configuration option to define your own translations directory (or directories):

		<framework:config>
		<framework:translator>
		<framework:path>%kernel.project_dir%/i18n</framework:path>
		<framework:default-path>%kernel.project_dir%/i18n</framework:default-path>
		</framework:translator>
		</framework:config>

Expand All		@@ -179,9 +179,7 @@ configuration option to define your own translations directory (or directories):
		// config/packages/translation.php
		$container->loadFromExtension('framework', [
		'translator' => [
		'paths' => [
		'%kernel.project_dir%/i18n',
		],
		'default_path' => '%kernel.project_dir%/i18n',
		],
		]);

Expand All		@@ -192,7 +190,7 @@ Override the Public Directory
		-----------------------------

		If you need to rename or move your ``public/`` directory, the only thing you
		need to guarantee is that the path to the ``var/`` directory is still correct in
		need to guarantee is that the path to the ``vendor/`` directory is still correct in
		your ``index.php`` front controller. If you renamed the directory, you're fine.
		But if you moved it in some way, you may need to modify these paths inside those
		files::
Expand Down