Translation improvements and shortenings

[TheKlem]

JIRA

https://jira.jahia.org/browse/PROJECT-XXX

Description

Tests

The following are included in this PR

• Unit Tests (Most changes should have unit tests)
• Integration Tests

Checklist

I have considered the following implications of my change:

• Security (in particular for changes to authentication, authorization, data fetching, ...)
• Performance
• Migration
• Code maintainability

Documentation

• Inline documentation
• Internal Documentation (wiki)
• User-facing Documentation

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Translation improvements and shortenings". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Sample valid messages:

A PR introducing a breaking change(!)

feat!: send an email to the customer when a product is shipped

A regular commit

docs: correct spelling of CHANGELOG

This message will be deleted once the PR title conforms with the convention.