Fix grammar and punctuation in package.nls.json
Addresses grammatical errors and missing punctuation in localization strings that impact readability and natural language processing for AI assistants.
Changes
-
Line 15: Removed incorrect "as" preposition
-
"named as GitHub Pull Request"→"named GitHub Pull Request"
-
-
Line 98: Added missing sentence-ending period
-
"if known"→"if known."
-
Original prompt
This section details on the original issue you should resolve
<issue_title>Incorrect and error riddled instructions.</issue_title> <issue_description># Patently incorrect grammar
https://github.com/microsoft/vscode-pull-request-github/blob/5f48d915f83b15fd28eca209acf4f9b5789f76cd/package.nls.json#L15
Incomplete sentences
https://github.com/microsoft/vscode-pull-request-github/blob/5f48d915f83b15fd28eca209acf4f9b5789f76cd/package.nls.json#L81
Incorrect handling of proper nouns
https://github.com/microsoft/vscode-pull-request-github/blob/5f48d915f83b15fd28eca209acf4f9b5789f76cd/package.nls.json#L98
Lack of humility
https://github.com/microsoft/vscode-pull-request-github/pull/7355#pullrequestreview-3037496961
Impact on AI assistants
The unacceptably poor writing in Microsoft documentation negatively impacts the performance of Copilot: a product I pay for. Microsoft refuses to pay for professional writing, and the results are predictable. microsoft/vscode-pull-request-github#7355 was not an altruistic act. I was trying to mitigate the effects of crappy writing on the responses I get from Copilot.
Competent writing
Until Microsoft implements basic checks to prevent incompetent writing, Microsoft should learn to recognize competent writing and graciously accept free labor from an experienced and highly trained writer.
Litmus test
- Can the inclusion or omission of a full stop affect the performance of machine natural language processing?
- If so, in which situations should one include or omit a full stop?
A writer who does not know the answers to these questions and many related questions is incapable of consistently drafting competent copy.</issue_description>
Comments on the Issue (you are @copilot in this section)
@alexr00 @hunterhogan I would recommend creating the issue before creating the PR and linking the issue in your PR In the future. The PR description did not give me an idea of why you created the PR and thus didn't give me a reason to accept the PR.@alexr00 I'm sure it depends on the project, but here issues are not considered to be confrontational.
- Fixes microsoft/vscode-pull-request-github#7362
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.