Skip to content

Invert section wording about headers to match content#5938

Open
veganaiZe wants to merge 1 commit into
MicrosoftDocs:mainfrom
veganaiZe:patch-1
Open

Invert section wording about headers to match content#5938
veganaiZe wants to merge 1 commit into
MicrosoftDocs:mainfrom
veganaiZe:patch-1

Conversation

@veganaiZe

Copy link
Copy Markdown

The section heading for "What to put in a header file" is misleading because all of its content is actually about what to avoid placing in a header file. It can especially be a problem for people skimming through who immediately jump to the bullet-list which, again, are things not to be included in a header.

This PR clarifies the section heading by changing it from "What to put in a header file" to "What to avoid in a header file".

Clarify intent of section
@prmerger-automator

Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit c1c92c8:

✅ Validation status: passed

File Status Preview URL Details
docs/cpp/header-files-cpp.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner

Copy link
Copy Markdown
Contributor

@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

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged Tracking label for the PR review team label Jun 12, 2026

@TylerMSFT TylerMSFT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Appreciate the update.

@TylerMSFT

Copy link
Copy Markdown
Collaborator

#sign-off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants