Tweaks for C6030 warning page

[Rageking8]

Summary:

• Remove extra space character in header
• Add links for [[noreturn]] and __declspec(noreturn)
• Move "Code analysis name" to its own line (every other instance does it that way)
• Remove superfluous trailing empty line in both code snippets
• Format [[ noreturn ]] and the function name (prefer snake case for uniformity)

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 423c0f3:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/code-quality/c6030.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Rageking8]

Just noticed that inline code blocks in link text does not affect the rendered output. For example both of these lines would look the same:

[__declspec(noreturn)](https://learn.microsoft.com/en-us/cpp/cpp/noreturn?view=msvc-170)
[`__declspec(noreturn)`](https://learn.microsoft.com/en-us/cpp/cpp/noreturn?view=msvc-170)

However, on GitHub there is a visible difference:

__declspec(noreturn)
__declspec(noreturn)

So should we prefer the former or latter?

[ttorble]

@TylerMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

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

[TylerMSFT]

Just noticed that inline code blocks in link text does not affect the rendered output. For example both of these lines would look the same:

[__declspec(noreturn)](https://learn.microsoft.com/en-us/cpp/cpp/noreturn?view=msvc-170)
[`__declspec(noreturn)`](https://learn.microsoft.com/en-us/cpp/cpp/noreturn?view=msvc-170)

However, on GitHub there is a visible difference:

__declspec(noreturn) __declspec(noreturn)

So should we prefer the former or latter?

The latter (use backticks). The reason is that the backticks prevent automatic machine translation and we don't want translation to happen here. The automatic translator is often smart enough not to try, but rather than play whack-a-mole trying to outsmart it, I default to using the backticks.

[TylerMSFT]

Thank you

[TylerMSFT]

#sign-off