Avoiding Translation Errors.

[0xanon]

You may add Google translator to the the possible places to enhance people understanding for every single language.

[welcome[bot]]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[madiedgar]

This is a great idea @0xanon ! Part of the reason why we're asking for native speakers for this project is to fill in the gaps that Google Translate can't, which is context of use. Incorporating Google Translate or like translators would likely be a feature in the future when we branch out past just keywords 👍