Fixed inconsistent spelling of "newline"

[weijuwang]

"newline" was spelled as "new-line" two out of four times in the documentation.

[prmerger-automator]

@weijuwang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[opbld33]

Docs Build status updates of commit aa9156b:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/c-language/lexical-grammar.md	✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[Jak-MS]

@corob-msft - Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[colin-home]

@weijuwang
Thanks for pointing out the inconsistency and proposing a fix. You have the right idea, but you've fixed the wrong targets. Ordinarily, I'd accept this PR, because the common term we use in the rest of the documentation is "newline". However, the C lexical grammar page quotes Annex A of the C17 Standard, which uses "new-line" everywhere. To be consistent, we should change the two cases of "newline" to "new-line". I'll approve and merge the PR if you make those changes. Thank you again for taking the time to make the docs better.

[prmerger-automator]

@weijuwang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[weijuwang]

Should be fixed now. Thanks for the response!

[opbld32]

Docs Build status updates of commit 2bc0468:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/c-language/lexical-grammar.md	✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[colin-home]

Looks good to me. Thanks for the quick turnaround, @weijuwang