Proof of Concept: Rename “Reject” to “Request Changes”

When a user starts translating and the reviewer rejects one of his or her translations, the translator may feel bad, even as a personal issue, about the rejection of his or her work.
To reduce the aggressiveness of the action and try to have a more positive translation environment, we have created a “proof of concept” (PR here), where we changed the word “Reject” to “Request changes”.
We want community members to review the change, which only affects the visual part, and give us your feedback. Below, you can see a series of screenshots of what the current situation looks like and what the proposed changes are.

Current situation

Reject button.
Reject filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..
List with the rejected stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings..
Rejection color.

Proposal changes

We propose to rename the “Reject” word to “Request Changes”. In a future, these changes could be added to the GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

“Request changes” button.
“Changed Requested” filter, with the “Request changes” strings and the new color.

#poc