Skip to content

Commit 0264998

Browse files
authored
fix ci
1 parent 9fdb644 commit 0264998

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

translation.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ different formats:
164164
'Symfony is great' => "J'aime Symfony",
165165
];
166166
167-
You can find more informations on where these files
167+
You can find more information on where these files
168168
:ref:`should be located <translation-resource-locations>`.
169169

170170
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
251251
using the ``trans()`` method:
252252

253253
#. 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
255255
your routes <translation-locale-url>`;
256256

257257
#. A catalog of translated messages is loaded from translation resources
@@ -1055,7 +1055,7 @@ unused translation messages templates:
10551055

10561056
The extractors can't find messages translated outside templates (like form
10571057
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
10591059
(since Symfony 5.3). Dynamic translations using variables or expressions in
10601060
templates are not detected either:
10611061

0 commit comments

Comments
 (0)