Fix typos in Private Tab

[simoarpe]

Resolves brave/brave-browser#41848

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

[SergeyZhukovsky]

I believe we should use a double dash as well in that place — instead of -, right @timchilds?

[timchilds]

That's my understanding. cc our resident dash expert @rmcfadden3 to confirm.

[rmcfadden3]

Official style is em dashes, no spaces. So:

Note that—even in private windows—your browsing activity…

[simoarpe]

I've made the necessary adjustments to the text as requested. However, I would like to kindly mention that, although I understand the use of em dashes is grammatically correct in American English, as a non-native speaker, this style can be somewhat concerning. It has the potential to cause significant confusion for individuals whose primary language is not American English. Perhaps, a more universal and easily understood form could be achieved using commas instead.

[SergeyZhukovsky]

I agree with @simoarpe , we will definitely have confusions after translation to other languages.

[timchilds]

WDYT @AndyAnds265 ?

[AndyAnds265]

hey all, sorry I missed this comment.

the localized side can be customized in the strings so unless something is hardcoded we should be able to edit by language

[simoarpe]

At this point, wouldn't it be better to get rid of the dashes in favor of commas for all the languages?
Benefits:

• More consistent style across all the languages
• International users that keeps Brave in English (like myself) would find it easier to read. (In many languages dashes don't exist)

[timchilds]

Let's go with commas for the reasons @simoarpe highlighted.

[bsclifton]

++ from string reviewers based on comment from @timchilds #26316 (comment)

[brave-builds]

Released in v1.75.18