C26135: Update comments to use correct annotation

[winstliu]

The lock is the critical section, not the pointer to it.

By the way, the contributing guide is outdated as it continues to make references to Issues, even though this repository has them disabled. What is the new way to start discussions as listed in the do's/don'ts section?

[prmerger-automator]

@winstliu : 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 2b20c4c:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/code-quality/c26135.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

[Jak-MS]

@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]

@winstliu - thank you for fixing this.

even though this repository has them disabled. What is the new way to start discussions as listed in the do's/don'ts section?
Some repos still use GitHub issues, though the C++ docs repo doesn't. To provide feedback on the C++ docs, please use the feedback button in the top right of the help topic page. That will generate a work item that shows up in my queue.

[TylerMSFT]

#sign-off