Misc markdown rules fixes for 7.5 #11521
Conversation
ExpectationsThanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it. To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details. The docs team begins to review your PR if you request them to or if your PR meets these conditions:
You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge. While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST). |
| Event Tracing for Windows (ETW) writes events to the log as events occur. The events are stored in | ||
| the order of oldest to newest. An archived ETW file is saved as an `.etl` such as **TraceLog.etl**. | ||
| The events are listed in the order in which they are written to the log, so the *Oldest* parameter | ||
| The events are listed in the order in which they are written to the log, so the `Oldest` parameter |
There was a problem hiding this comment.
Parameter names should be bold.
| The events are listed in the order in which they are written to the log, so the `Oldest` parameter | |
| The events are listed in the order in which they are written to the log, so the **Oldest** parameter |
| ### -AdditionalChildPath | ||
|
|
||
| Specifies additional elements to append to the value of the *Path* parameter. The `ChildPath` | ||
| Specifies additional elements to append to the value of the `Path` parameter. The `ChildPath` |
There was a problem hiding this comment.
| Specifies additional elements to append to the value of the `Path` parameter. The `ChildPath` | |
| Specifies additional elements to append to the value of the **Path** parameter. The **ChildPath** |
| Implementation varies from provider to provider. | ||
| For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). | ||
| Even using the *Force* parameter, the cmdlet cannot override security restrictions. | ||
| Even using the `Force` parameter, the cmdlet cannot override security restrictions. |
There was a problem hiding this comment.
| Even using the `Force` parameter, the cmdlet cannot override security restrictions. | |
| Even using the **Force** parameter, the cmdlet cannot override security restrictions. |
|
Learn Build status updates of commit 8f7e164: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
sorry..was working on mutiple branches at same time and managed to ruin this one. will resubmit :( |
2 participants
PR Summary
Majority are MD049 Emphasis. replacing text with text per MD rules
Few MD038 for extra spaces in code
Two left overs MD026 and MD31 from previous sessions.
Adjusted to fix original Formatting problems
PR Checklist