Wrong translation in Spanish for "Learn about Tertiary Colors"
See original GitHub issueAffected page Add a link to the coding challenge with the problem.
In the second to last test, the text is:
El elemento `div` con clase `raspberry` debe tener un `background-color` naranja.
The word “naranja” means “orange” - it should be “frambuesa”.
In the file:
freeCodeCamp/main/curriculum/challenges/espanol/01-responsive-web-design/applied-visual-design/learn-about-tertiary-colors.md
Your code Copy and paste the code from the editor that you used in between the back-ticks below:
El elemento `div` con clase `raspberry` debe tener un `background-color` frambuesa.
Expected behavior Add a clear and concise description of what you expected to happen.
I expect the color raspberry to be translated into Spanish as “frambuesa”, not “naranja”.
Screenshots
N/A
System (please complete the following information):
N/A
Additional context
I’m just relaying a report from the forum. If someone wants to grab this, they’re welcome.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top GitHub Comments
Hello, Spanish proofreader here. Thanks for pointing this out, Kevin! I already fixed it on Crowdin, hope that it updates on production soon.
We have had teams and groups on Crowdin from day one, they seem to be utilized I think. It’s perfectly okay to report issues in any of the channels Chat, Forum or GitHub and someone will get to it.
However, the idea should be not to duplicate the report in other channels. So, if we get a report on the forum we can simply tag someone (even someone in the staff) to draw their attention.
@juancarrillofl thanks for fixing the issue.
Usually, it takes 1-2 days for us to pull changes and deploy them live, but it could take longer depending on workload & other factors.