-
Notifications
You must be signed in to change notification settings - Fork 967
Minor styling fixes #4420
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
Minor styling fixes #4420
Conversation
X0RW3LL
commented
Feb 16, 2023
- Preserve new lines
- Emphasize list items for readability
- Preserve new lines - Emphasize list items for readability
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
4 similar comments
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit c3997a6: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
PRMerger Results
|
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
@corob-msft Can you review the proposed changes? When the changes are ready for publication, add a #label:"aq-pr-triaged" |
@X0RW3LL : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
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.
@X0RW3LL
Thanks for the update. It looks like this was missed in some long-ago formatting conversion to markdown, along with some others. Lots of others, in fact, since we've been finding and fixing similar issues for years. The two files you found and about three others I found with a regex still have the problem. Fixes should move through the publishing pipeline and appear tomorrow.
@corob-msft Thank you so much for the update! I do apologize for the separate PRs—I noticed the issue while actively reading, and I thought sending PRs separately would highlight a potentially recurring issue. Once again, thank you, @Court72, and everyone on the team! I do hope I can make more contributions in the future :) P.s Microsoft Learn is a wonderful thing, and I appreciate the massive amount of work everyone's put into it |