strings.xml improvements and small rephrasals

[nvllz]

Pull request (PR) checklist

Please check if your pull request fulfills the following requirements:

• I've read the Contribution Guidelines and my PR doesn't break the rules.
• I've read and understand the Developer Guidelines.
• I confirm that I've run the code locally and everything works as expected.
• My PR includes only the necessary changes to fix the issue (i.e., no unnecessary files or lines of code are changed).
• 🎬 I've attached a screen recording of using the new code to the next paragraph (if applicable).

What's changed?

Describe with a few bullets what's new:

• tried to make some strings more user friendly
• fixed grammar/spelling errors

Does this PR close any GitHub issues? (do not delete)

• Closes N/A

[ILIYANGERMANOV]

Thanks for the improvements! Merging after the CI pass

[ILIYANGERMANOV]

@nvllz you need to update the screenshot tests because you modified an UI see the CI Troubleshooting guide

[nvllz]

@ILIYANGERMANOV Is there a way to return all paparazzi errors at once? Or do I have to debug and record them one by one? I mean if I knew which screens to record I could easily do it in bulk, now I have to wait 7 minutes to know which next screen (you name it module in your docs/faq/guidelines) is gonna throw an error. Sorry for my ignorance, but this is overkill.