Removes output from Examples that break the docs

[MikeyBronowski]

Type of Change

• Bug fix (non-breaking change, fixes # )
• New feature (non-breaking change, adds functionality, fixes # )
• Breaking change (effects multiple commands or functionality, fixes # )
• Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
• Adding code coverage to existing functionality
• Pester test is included
• If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
• Unit test is included
• Documentation
• Build system

Purpose

The docs are broken by this format, plus other examples do not include outputs.

Approach

Commands to test

Screenshots

Learning

[andreasjordan]

I'm totally fine with removing the output.

[niphlod]

all it takes is prefixing the output with > to not break the docs, IMHO having an example of what the command gives back is super-useful.

[potatoqualitee]

Thank you, @niphlod . @MikeyBronowski would you be able to prefix the output with > instead? 🙏🏼

[MikeyBronowski]

Thank you, @niphlod . @MikeyBronowski would you be able to prefix the output with > instead? 🙏🏼

Sure. Will do that.

[MikeyBronowski]

@potatoqualitee @niphlod done

[potatoqualitee]

awessome thank you all!