fix(ui): Capitalization, punctuation, and grammar inconsistences & errors

[TheCatLady]

@sct: I understand this is a huge PR that touches a ton of files, so I totally understand if you don't want to accept it, but I figured I'd try before the project got any bigger.

Description

I have OCD and inconsistencies and errors really bother me. I feel that especially as Overseerr matures, we need a style guide for UI text. The codebase is uniformly/consistently formatted, so let's make the UI that way as well!

I propose that:

• Appropriate Unicode characters are used for ellipses, arrows, etc.
• Proper nouns (Plex, Radarr, Sonarr, Telegram, Slack, Pushover, etc.) are capitalized
• Headings, button text, and form labels are title case (verbs like "is" should be capitalized, whereas prepositions like "from" should not)
• First letter is capitalized in validation error messages, dropdowns, and form "tips"
• Toast notifications are complete sentences ending in some form of punctuation
• If an additional description/"tip" is required for a field, it should be separate from the main label
• In full sentences, abbreviations like "info" or "auto" should not be used in place of full words, unless referencing the name/label of a setting/option which has an abbreviation
• Since a decision was made to use "sign in/out" in another PR, let's be consistent and not use "log in/out" verbiage
• Correct capitalization is used for the names of metadata databases... TMDb and IMDb officially have a lowercase 'b', while TVDB has a capital 'B' (infuriating, I know, but let's stick with what's official!)
• There are no grammatical mistakes (of course)
• Oxford comma is used where appropriate
• Be concise and clear, using as few words as possible to make your point
• "Overseerr" is not misspelled 🤦🏻‍♀️ (...and it should be capitalized since it's a proper noun!)

If there are any other issues that I didn't catch, please let me know and I can add them to this PR. 😺

And I'd be happy to help proofread/review any PRs that introduce new UI strings going forward; just tag me!

Screenshot (if UI related)

Example:

[lgtm-com]

This pull request introduces 1 alert when merging 6c04b6b into 2f75c4c - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[spylex]

Purely from an effort perspective and for neatness i suggest this gets merged, and TheCatLady onboarded as official formatting guru!

[github-actions]

🎉 This PR is included in version 1.18.0 🎉

The release is available on:

• v1.18.0
• GitHub release

Your semantic-release bot 📦🚀