Change:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
I can take this one
Awesome! All yours.
should I translate all the files or just one?
I would recommend starting one by one and making a separate PR for each. Also, please note that we rapidly iterating over the english versions at the moment. So, take your time and revisit this issue thread for changes.
I will start working on If anyone else wants to help, feel free to.
Hello! I can also help out translating. I will get started with the !
Hey! I can translate the next file how-to-catch-outgoing-emails-
Hey guys! I can translate the how-to-work-on-coding- one :)
And I can finish up with how-to-work-on-guide-!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
I can work on how-to-setup-freecodecamp- Also, there is a substantial difference between PT-PT and PT-BR (Portuguese from Portugal and Portuguese from Brazil). Maybe there should be different translations for each one?
I agree with PT-PT and PT-BR have many differences and it would be nice to have both made separately
There are some differences but it is very easy to understand for both PT-BR and PT-PT speakers, in my opinion. I don't mind reading in PT-BR and I would guess the opposite also happens?
Hi All, Thanks a lot for taking the time to contribute to At the minute we are making the translations available in the PT-BR. We might consider PT-PT in future, but I am afraid we don't have an ETA on that. Thanks.
Is there still missing translations for this issue?
Is there any missing translation? I would like to help
I'll be helping on this one. Just one question, should we translate PT-PT to PT-BR? For example, in PT-PT "corre" means execute, but it has totally different meaning in PT-BR (sprint). In this case, I would substitute it by "executa", the correct translation.
Is the issue completed? I can also help with any Portuguese translations.
I can help as well, if it's still needed.
Hey! I'm gonna start working on how-to-work-on-guide- !
Hello folks, I can assist with PT-BR
Hi! I fixed links on the portuguese and took the chance to also do it on the english version (links did not work).
I'm learning Github and have just figured out how to search through the issues for code commits that might apply and found this. My pull request fixes many of the md links for each of the language documents and adds Portuguese to the top language links bar to all of them, specifically directing to the correct language links README file. No translation, just link fixes ;p
There are 2 docs not listed in the Issue, but with no PT-BR translation. Can I get one of those?
hey what about us divide this one. I could pick the second one: .
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

Discussion:
<ins> <table> <tr> <td> Read these guidelines in </td> <td><a href="/CONTRIBUTING.md"> English </a></td> <td><a href="/docs/chinese/CONTRIBUTING.md"> 中文 </a></td> <td><a href="/docs/russian/CONTRIBUTING.md"> русский </a></td> <td><a href="/docs/arabic/CONTRIBUTING.md"> عربى </a></td> <td><a href="/docs/spanish/CONTRIBUTING.md"> Español </a></td> <td><a href="/docs/portuguese/CONTRIBUTING.md"> Português </a></td> </tr> </table> </ins> # Como obter localmente os emails enviados (para fluxos de emails) > **Nota:** Este passo é **opcional** - Obrigatório apenas quando estiver trabalhando com fluxos de emails