Localization-for-developers.md

@@ -38,19 +38,21 @@ If this is the first time you are implementing the internationalization of a pro
 
 It may sound efficient in English, but the truth is that different languages have different ways of saying things, and the order is important. Please make it so the whole sentences is up for translation at once, don't separate sentences in several strings.
 
+For example, is better to have 'Good morning' and 'Good afternoon' to translate, than 'Good', 'morning' and 'after'. Although you can still get good translations with 'Good $', 'morning', and 'after'.
+
 #### 2. PUNCTUATION IS PART OF THE SENTENCE
 
 Please add all punctuation for translation, as different languages use different punctuation rules. Punctuation is part of the sentence.
 
 #### 3. NO HARDCODED UPPERCASES OR CAPITALIZATION
 
-In many languages, ortographic rules change depending on a word being capitalized or not. As Greek and Russian. Other languages, like Arabic, don't even have capital letters, so your styling will not be seen.
+In many languages ortographic rules change depending on a word being capitalized or not. As Greek and Russian. Other languages, like Arabic, don't even have capital letters, so your styling will not be seen.
 
-That is why you should refrain from hardcoding this styles on CSS or other similar way. If you want a capitalized sentence, write the actual sentence capitalized as you would like to see it, so the translator understands what you want, and translates your intention on the local rules (maybe adding exclamation signs).
+That is why you should refrain from hardcoding styles like all caps or camel case on CSS or other similar way. If you want a capitalized sentence, write the actual sentence capitalized as you would like to see it, so the translator understands what you want, and translates your intention on the local rules (maybe adding exclamation signs).
 
 #### 4. ADD COMMENTS OR EXPLANATIONS ON HOW TO TRANSLATE
 
-Context is everything when translating, and if a string has many errors, it probably means that a developer comment explaining how to translate it is needed. 
+Context is everything when translating, and if a string has many errors, it probably means that more context is needed. 
 
 Some strings need screenshots to be well translated. Especially in GUIs, when we translate out-of-context single words. 
 
@@ -58,6 +60,8 @@ When the source text is in English, as on our project, the objects on that langu
 
 Weblate also provides [QA checks](https://docs.weblate.org/en/latest/user/checks.html). This has the advantage of providing structured feedback to translators while they are translating. You can see our [failing checks in weblate](https://hosted.weblate.org/checks/-/tor/).
 
+If Weblate is not catching and error of the translation, please let the Localization Coordinator know, as this could be solved.
+
 #### 5. PROVIDE SCREENSHOTS AND EARLY LOCALIZED RESOURCES
 
 The translators will translate better if they can see the effect their translations have. Try to get a staging/beta version early, so they can do a final review for the language with the real application.