@@ -168,7 +168,7 @@ <h2>The English Translation</h2>
168168
169169 In Fluent, most messages are simple text strings identified by
170170 an < em > identifier</ em > . In the first message in the example,
171- < code > tabs-close-button</ code > is an identifier and
171+ < code > tabs-close-button</ code > is the identifier and
172172 < code > Close</ code > is the value.
173173
174174 </ p >
@@ -179,7 +179,7 @@ <h2>The English Translation</h2>
179179 < code > tabs-close-tooltip</ code > message, the correct variant of
180180 the translation depends on the value of the
181181 < code > $tabCount</ code > variable. The names of the variants,
182- < code > [one]</ code > and < code > [other]</ code > are standard names
182+ < code > [one]</ code > and < code > [other]</ code > , are standard names
183183 of the plural categories defined by the Unicode in < a
184184 href ="http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html "> CLDR</ a > .
185185
@@ -244,9 +244,10 @@ <h2>The Italian Translation</h2>
244244 < p >
245245
246246 At the same time, the < code > [lowercase]</ code > variant can be
247- explicitly requested by passing the < code > first</ code >
248- parameter when the brand name is used inside a larger sentence
249- in the < code > sync-signedout-title</ code > message.
247+ explicitly requested by passing the < code > first:
248+ "lowercase"</ code > parameter when the brand name is used inside
249+ a larger sentence in the < code > sync-signedout-title</ code >
250+ message.
250251
251252 </ p >
252253 </ div >
@@ -259,24 +260,24 @@ <h2>The Polish Translation</h2>
259260
260261 < p >
261262
262- The Polish translation illustrates how yet more complex
263- grammars can be catered to in Fluent .
263+ The Polish translation illustrates how Fluent caters to yet
264+ more complex grammars .
264265
265266 </ p >
266267 < p >
267268
268269 The imperative < em > Close</ em > command in
269270 < code > tabs-close-button</ code > , < em > Zamknij</ em > , still remains
270- a simple string, but the other messages in the
271- < code > tabs-close</ code > group require a bit more attention to
272- sound well in Polish. It's related to the fact that Polish, a
273- Slavic language, has more plural categories than English (a
274- Germanic language) or Italian (a Romance language). For
275- example, the Polish translation for < em > tab </ em > takes
276- different forms for counts of 2, 3, and 4 than it does for 5,
277- 6, or 7. Hence, the < code > tabs-close-warning </ code > message
278- requires additional variants in Polish: < code > [few] </ code > and
279- < code > [many]</ code > .
271+ a simple string, same as in English and in Italian. The other
272+ messages in the < code > tabs-close</ code > group, however, require
273+ a bit more attention to sound well in Polish. It's related to
274+ the fact that Polish, a Slavic language, has more plural
275+ categories than English (a Germanic language) or Italian (a
276+ Romance language). For example, the Polish translation for
277+ < em > tab </ em > takes a different form for counts of 2, 3, and 4
278+ than it does for 5, 6, or 7. Hence, the
279+ < code > tabs-close-warning </ code > message requires additional
280+ variants in Polish: < code > [few] </ code > and < code > [many]</ code > .
280281
281282 </ p >
282283 < p >
@@ -291,10 +292,10 @@ <h2>The Polish Translation</h2>
291292 </ p >
292293 < p >
293294
294- Using terms verbatim in sentences requires care in Polish,
295- which is an inflected language.
296- The Polish translation uses declensions to construct a
297- grammatically correct sentence in the
295+ Using terms inside sentences requires care in Polish, which is
296+ an inflected language. The Polish translation can reference the
297+ specific term variant corresponding to the < em > genitive </ em >
298+ declension to construct a grammatically correct sentence in the
298299 < code > sync-signedout-title</ code > message.
299300
300301 </ p >
0 commit comments