Skip to content

Commit

Permalink
Update How-To-Add-Translations.md
Browse files Browse the repository at this point in the history
Fixed typos and imrpoved readbility
  • Loading branch information
abhishek213-alb authored Oct 27, 2023
1 parent 4340db1 commit 40da077
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/How-To-Add-Translations.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
This document outlines how to add support for various local languages in Phoenix.

Phoenix currently supports over 35 languages and are mostly automatically translated with AWS/Google translate.
Phoenix currently supports over 35 languages, primarily through automatic translations using AWS/Google Translate.

## Quick start

Expand All @@ -22,7 +22,7 @@ This folder contains all the localised strings. Each sub folder corresponds to a
A special folder called the `root` folder houses the reference english translations from which all other locale
translations are derived. The `root` folder has three main files:
1. `strings.js` - The full list of translated text.
2. `strings-app.js` - The list of language code to localised language name mapping. This will be used in the switch
2. `strings-app.js` - The list of language code to localized language name mapping. This will be used in the switch
language dialogue in debug menu.
3. `urls.js` - local specific URLs.

Expand Down Expand Up @@ -69,4 +69,4 @@ Say we want to add a new language translation `ko`. We have to do the following

Once the code is checked in, the translation will be auto generated.

> NB: For internal devs, You may manually generate the translation with `npm run _translateStrings` if you have the necessary keys for translation.
> NB: For internal developers, You may manually generate the translation with `npm run _translateStrings` if you have the necessary keys for translation.

0 comments on commit 40da077

Please sign in to comment.