-
Notifications
You must be signed in to change notification settings - Fork 967
Fix some unclosed links #5222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix some unclosed links #5222
Conversation
@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit a664524: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@@ -22,7 +21,7 @@ class invalid_scheduler_policy_thread_specification : public std::exception; | |||
|
|||
|Name|Description| | |||
|----------|-----------------| | |||
|[invalid_scheduler_policy_thread_specification](invalid-scheduler-policy-value-class.md#ctor|Overloaded. Constructs an `invalid_scheduler_policy_value` object.| | |||
|[invalid_scheduler_policy_thread_specification](#ctor)|Overloaded. Constructs an `invalid_scheduler_policy_thread_specification` object.| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drive-by fix where invalid_scheduler_policy_thread_specification
and invalid_scheduler_policy_value
were mixed up.
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great - thank you! This will also help with the broken link report, so double thank you.
#sign-off |
@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Unclosed link fixes and metadata changes are in the first commit, while cleanups and updates are split into multiple other ones to keep things clean. Hence, it's better to review one commit at a time.
Updates (for second commit onwards):
br
elements with escapescpp
as language to code blocks