Skip to content

Remove extraneous spaces after hyphen character #5487

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Rageking8
Copy link
Contributor

Remove extraneous spaces after hyphen character and update metadata.

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 127ca8d:

✅ Validation status: passed

File Status Preview URL Details
docs/build/arm-exception-handling.md ✅Succeeded
docs/error-messages/compiler-errors-2/compiler-error-c2548.md ✅Succeeded
docs/sanitizers/asan-shadow-bytes.md ✅Succeeded
docs/standard-library/string-functions.md ✅Succeeded
docs/standard-library/valarray-class.md ✅Succeeded

For more details, please refer to the build report.

@@ -167,7 +166,7 @@ When the packed unwind format is insufficient to describe the unwinding of a fun
|0|20|*X* is a 1-bit field that indicates the presence (1) or absence (0) of exception data.|
|0|21|*`E`* is a 1-bit field that indicates that information that describes a single epilogue is packed into the header (1) rather than requiring additional scope words later (0).|
|0|22|*F* is a 1-bit field that indicates that this record describes a function fragment (1) or a full function (0). A fragment implies that there's no prologue and that all prologue processing should be ignored.|
|0|23-27|*Epilogue Count* is a 5-bit field that has two meanings, depending on the state of the *`E`* bit:<br /><br /> - If *`E`* is 0, this field is a count of the total number of epilogue scopes described in section 2. If more than 31 scopes exist in the function, then this field and the *Code Words* field must both be set to 0 to indicate that an extension word is required.<br />- If *`E`* is 1, this field specifies the index of the first unwind code that describes the only epilogue.|
|0|23-27|*Epilogue Count* is a 5-bit field that has two meanings, depending on the state of the *`E`* bit:<br /><br />- If *`E`* is 0, this field is a count of the total number of epilogue scopes described in section 2. If more than 31 scopes exist in the function, then this field and the *Code Words* field must both be set to 0 to indicate that an extension word is required.<br />- If *`E`* is 1, this field specifies the index of the first unwind code that describes the only epilogue.|
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This follows the "convention" in this topic where there is no space between the br element and the hyphen, with one after.

@v-dirichards
Copy link
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 Jul 2, 2025
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