Localization-for-developers.md

@@ -5,7 +5,7 @@ Localizing our software let us share it with more people, and should eventually
 
 If you have doubts about how to localize your software, please get in touch with emmapeel@torproject.org
 
-### Table of contents
+**Table of contents**
 
 [[_TOC_]] 
 
@@ -14,7 +14,7 @@ If you have doubts about how to localize your software, please get in touch with
    Remember that **if you generate better quality source strings, the translations will be better**.
 
 
-## Translators' input
+### Translators' input
 
 Translators find many errors on the source strings, it is important to have a look at the [open issues in transifex](https://www.transifex.com/otf/torproject/translate/#issues) (needs login)
 
@@ -24,21 +24,21 @@ After selecting a string, check the Comments section on the bottom right: there
 
 Please read the incredibly good article [https://www.smashingmagazine.com/2012/07/12-commandments-software-localization/ 12 Commandments Of Software Localization] from Zack Grossbart to get an introduction to software localization from an engineer's point of view. This are developers best practices with l10n in mind:
 
-### 1. NEVER CONCATENATE STRINGS 
+#### 1. NEVER CONCATENATE STRINGS 
 
 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.
 
-### 2. PUNCTUATION IS PART OF THE SENTENCE
+#### 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
+#### 3. NO HARDCODED UPPERCASES OR CAPITALIZATION
 
 Ortographic rules change depending on a word being capitalized or not in many languages, 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 of hardcoding this styles on CSS or other similar way, and 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
+#### 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.
 
@@ -46,7 +46,7 @@ You can also upload screenshots to the strings. That will improve greatly the qu
 
 When the source text is in English, as on our project, the objects on that language have no gender. But objects have gender in many languages: Spanish, Italian, French, German... So when we translate 'Published'  to German, we need to know what was published, to give the correct gender to the adjective.
 
-### 5. PROVIDE SCREENSHOTS AND EARLY LOCALIZED RESOURCES
+#### 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.
 
@@ -57,7 +57,7 @@ The localization coordinator can add the screenshots and map them to the strings
 
 Release an alpha to test translations as the Tor Browser team does. For the websites, we have separated versions with more languages so translators can preview their work.
 
-### Getting your translations added to Transifex
+# Getting your translations added to Transifex
 
 Imagine a timeline a bit like this:
 ```mermaid