Fixed formatting of output per issue #808

[sdwheeler]

The examples were confusing because of the way the output was formatted. Fixed formatting to be clearer about the contents of the CSV files.

See issue #808 for more info.

Version(s) of document impacted

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

[markekraus]

If I remember correctly, PlatyPS was failing when you have 2 code blocks in an example section (#1795). that is why they are in one block as a comment.

[saldana]

✅ Validation status: passed

File	Status	Preview URL	Details
reference/3.0/Microsoft.PowerShell.Utility/Export-Csv.md	✅Succeeded
reference/4.0/Microsoft.PowerShell.Utility/Export-Csv.md	✅Succeeded
reference/5.0/Microsoft.PowerShell.Utility/Export-Csv.md	✅Succeeded
reference/5.1/Microsoft.PowerShell.Utility/Export-Csv.md	✅Succeeded
reference/6/Microsoft.PowerShell.Utility/Export-Csv.md	✅Succeeded

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]

@markekraus It appears that Platyps has no problem with this now. See the attached file.
Microsoft.PowerShell.Commands.Utility.dll-Help.xml.zip

[markekraus]

@sdwheeler awesome news! I see the language spec for the block is Output, perhaps lacking that is what caused the issue. Anyway, good to know!

[sdwheeler]

@markekraus the Output "language" is not officially supported. However, OPS will use that to label the code box on the rendered webpage. It treats the code block as plain text with no highlighting. So it makes it clearer to the reader that we are dealing with output.