Fixes #12836 - Fix accuracy of the output in examples#12840
Fixes #12836 - Fix accuracy of the output in examples#12840sdwheeler merged 1 commit intoMicrosoftDocs:mainfrom
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit ecde2a2: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Updates the Get-Content reference documentation to ensure example outputs accurately reflect the example commands and generated file content across multiple PowerShell versions.
Changes:
- Fix example output lines to include trailing periods and consistent casing (
linevsLine) in multiple versions. - Update
ms.datemetadata to reflect the documentation change date. - (5.1) Wrap long comment lines in code blocks and fix casing in cross-reference links to
Microsoft.PowerShell.CoreAbout topics.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| reference/7.6/Microsoft.PowerShell.Management/Get-Content.md | Corrects example output text/formatting and updates ms.date. |
| reference/7.5/Microsoft.PowerShell.Management/Get-Content.md | Corrects example output text/formatting and updates ms.date. |
| reference/7.4/Microsoft.PowerShell.Management/Get-Content.md | Corrects example output text/formatting and updates ms.date. |
| reference/5.1/Microsoft.PowerShell.Management/Get-Content.md | Corrects example output text/formatting, wraps long comments, and fixes link casing; updates ms.date. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ```Output | ||
| This is Line 1 | ||
| This is Line 2 | ||
| This is line 1. | ||
| This is line 2. | ||
| ... | ||
| This is line 99. |
There was a problem hiding this comment.
In Example 1, the prose says the file uses the format "This is Line X", but the example code and the updated output show "This is line X." (lowercase "line" + trailing period). To keep the example accurate, update the description sentence to match the actual generated content/output format.
| ```Output | ||
| This is Line 1 | ||
| This is Line 2 | ||
| This is line 1. | ||
| This is line 2. | ||
| ... | ||
| This is line 99. |
There was a problem hiding this comment.
In Example 1, the description states the file format is "This is Line X", but the example code and updated output show "This is line X." (lowercase + trailing period). Please update the description to match the actual content/output so the example remains accurate.
| ```Output | ||
| This is Line 1 | ||
| This is Line 2 | ||
| This is line 1. | ||
| This is line 2. | ||
| ... | ||
| This is line 99. |
There was a problem hiding this comment.
In Example 1, the narrative says the file is formatted as "This is Line X", but the example code and updated output use "This is line X." (lowercase + period). Update the description text to align with the actual generated content/output.
| ```Output | ||
| This is Line 1 | ||
| This is Line 2 | ||
| This is line 1. | ||
| This is line 2. | ||
| ... | ||
| This is line 99. |
There was a problem hiding this comment.
In Example 1, the prose says the file lines are in the format "This is Line X", but the example command and the updated output are "This is line X." (lowercase + trailing period). Please update the description sentence to match the actual content/output format.
PR Summary
Fix accuracy of the output in examples
.lost in help file forGet-Content#12836PR Checklist