chore: Post-merge review of UI strings

Description

As requested in !1745 (comment 2231744787), doing a post-merge review of these release-related files. Let's bring this text closer to GitLab tone and style.

Related Issues

• Related to feat(release): "release create --publish-to-cat... (!1745 - merged) where the feature was introduced
• Related to Publish release to catalog command (#7679 - closed)

How has this been tested?

Screenshots (if appropriate):

Types of changes

• 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 change)
• Documentation
• Chore (Related to CI or Packaging to platforms)
• Test gap

Closes #7679 (closed)