Fixed formatting on expanded example

[Halkcyon]

The formatting on the MS page looks really convoluted with the expanded example so I changed the example into one large codeblock for consistent formatting

Version(s) of document impacted

• Impacts 6 document
• Impacts 5.1 document
• Impacts 5.0 document
• Impacts 4.0 document
• Impacts 3.0 document

Reason(s) for not updating all version of documents

• The documented feature was introduced in version (list version here) of PowerShell
• This issue only shows up in version (list version(s) here) of the document
• This PR partially fixes the issue, and issue # tracks the remaining work

[msftclas]

All CLA requirements met.

[saldana]

⚠️ Validation status: warnings

File	Status	Preview URL	Details
reference/5.1/Microsoft.PowerShell.Core/About/about_pipelines.md	⚠️Warning		Details

reference/5.1/Microsoft.PowerShell.Core/About/about_pipelines.md

• [Warning] Ignore metadata: locale. They are generated by open publish.

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

[sdwheeler]

@joeyaiello @zjalexander - What do you think about this formatting change?

[zjalexander]

I see the problem. I love the effort to think about it. I would like to either have the codeblocks be all plain or have just the ascii art blocked off and plain. I think all-plain is slightly better and easier, but would like some additional discussion.

[zjalexander]

hm, the above should probably be in a plain codeblock (no powershell language indicator) so the ASCII art doesn't get syntax highlighted? but then you would need to alternate between PS code blocks and plain code blocks? or just have the entire thing in plain codeblocks...

[Halkcyon]

Another solution I thought of in hindsight, having a code block in one example, and another below that code block with the object types of the pipeline (instead of the commands)

[sdwheeler]

@TheIncorrigible1 - Thank you for your contribution. After some deliberation I am closing this PR unmerged. We talked about this internally and liked some of the changes you made and we had other ideas. I had to reformat this topic as part of the issue #1806 efforts. So I incorporated this into my changes.

cc: @zjalexander