Fix awkwardly translated string

[respencer]

Description & Issue number it closes

Resolves #2776

Screenshots (if appropriate)

Before:

After:

How to test the changes?

Visual inspection.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Visual inspection.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[DawoudIO]

Please do not merge

[DAcodedBEAT]

Please do not merge

@DawoudIO is there a reason for blocking this? If possible, I think code reviews should be as descriptive as possible and your response doesn't indicate what is wrong with the suggested change.

[respencer]

@DawoudIO: Do I need to abandon this PR?

[DawoudIO]

No, sorry for putting it on hold... I think "MailChimp is not configured" should remain as "is not configured," but I understand that some languages have different placements for it... I'm ok moving forward with it

[DawoudIO]

We need to document the following:

1. we need to run the following command npm run locale-gen to regen the new file
2. upload the locale/messages.po to poeditor.com to update the terms, and delete any unused terms.
3. download the result via daily poeditor download or npm run locale-download if you have the poeditor API key