fix(l10n): add localization guidance comments for technical terms

[yeelam-gordon]

Summary of the Pull Request

Adds <comment>\ elements to \�n-US/Resources.resw\ providing translation guidance for technical terms that are frequently mistranslated:

• File formats (tar, VHD) should not be translated
• Technical terms (mount, swap, sparse, DNS, proxy) need locale-appropriate terms or should be kept as-is
• Safe mode should use standard OS terminology per locale

These comments help the localization team produce more accurate translations without directly modifying locale-specific files.

PR Checklist

• Ref: Mistranslations & Typos in Turkish translation still exist #14090
• Localization: Adds guidance comments to source strings for better localization quality

Validation Steps Performed

• XML parse validation passed
• Only \�n-US/Resources.resw\ modified (no locale files changed)

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Updates Turkish (tr-TR) localized strings to better align with the current en-US messaging and UI wording for WSL CLI output and Settings UI.

Changes:

• Refines multiple tr-TR CLI/status messages (wording, punctuation, and clarity) while preserving {} placeholder usage.
• Adjusts several Settings-related strings (e.g., GUI apps help text, ignored ports description) to better match en-US intent and formatting.

---

You can also share your feedback on Copilot code review. Take the survey.

[benhillis]

@yeelam-gordon - thanks for the fix. However these localization files are auto-generated so the correct way to fix them is to file a bug with the localization team. Reach out to me via Teams and I'll give you the link.

[yeelam-gordon]

@yeelam-gordon - thanks for the fix. However these localization files are auto-generated so the correct way to fix them is to file a bug with the localization team. Reach out to me via Teams and I'll give you the link.

@benhillis, very true. Let's take this offline to discuss contacting the localization team.
Fix now: add the correct "Comments" in the en-US file so the localization system knows what the original term means, helping them on localizing.

[yeelam-gordon]

BTW... interestingly, there was a PR really fix the localized resource file... #14057, I am confused.