@@ -164,7 +164,7 @@ different formats:
164
164
'Symfony is great' => "J'aime Symfony",
165
165
];
166
166
167
- You can find more informations on where these files
167
+ You can find more information on where these files
168
168
:ref: `should be located <translation-resource-locations >`.
169
169
170
170
Now, if the language of the user's locale is French (e.g. ``fr_FR `` or ``fr_BE ``),
@@ -251,7 +251,7 @@ To actually translate the message, Symfony uses the following process when
251
251
using the ``trans() `` method:
252
252
253
253
#. The ``locale `` of the current user, which is stored on the request is
254
- determined; this is typically set via a ``_locale `` :ref: `attribute on
254
+ determined; this is typically set via a ``_locale `` :ref: `attribute on
255
255
your routes <translation-locale-url>`;
256
256
257
257
#. A catalog of translated messages is loaded from translation resources
@@ -1055,7 +1055,7 @@ unused translation messages templates:
1055
1055
1056
1056
The extractors can't find messages translated outside templates (like form
1057
1057
labels or controllers) unless using :ref: `translatable objects
1058
- <translatable-objects>` or calling the ``trans() `` method on a translator
1058
+ <translatable-objects>` or calling the ``trans() `` method on a translator
1059
1059
(since Symfony 5.3). Dynamic translations using variables or expressions in
1060
1060
templates are not detected either:
1061
1061
0 commit comments