The first step in manually reviewing strings with errors is to filter to a specific error type.
Let’s start with “Spaces mismatch” since these are usually pretty easy to handle.
1. Set the filter to a specific error type
2. Review each translation
For the first translation in the list, the problem is minor but obvious:
Remove the space and you’ll be prompted to save that translation:
If you have the appropriate privileges as a proofreader, saving the translation will automatically mark it as approved:
Sometimes the Crowdin error check is wrong, and the string is really OK. In that case just click the checkbox button on the right to approve that string.
Repeat this for each string that has the current error type.
As you’re going through the translations you may spot some issues with the source strings in English. These need to be changed in the core code instead. You can report any such issues here:
3. Pick a different filter category
Using the same Filter menu from before, pick a different error type and follow the same process to review all strings. I’ve chosen “Filter > QA check > Spelling” here:
You may recognize that string from earlier, and it’s already marked as “Done” / “Approved”. Some of the same strings may have multiple error types. It looks like Crowdin doesn’t always show all of the errors at once when you are filtering this way. This isn’t ideal but it means that some strings with errors may be temporarily “approved” until all errors are reviewed.
Once this is done, you should have a green bar in the project dashboard for your chosen language, with no blue bar for “unapproved” strings. This language is now ready to accept contributions from anyone, and any new translations should show up as “unapproved” and ready to be reviewed using the same filters described above.