Broken link to list of approved verbs

[antoniouaa]

The link was missing part of the URL that redirected to the MS docs.
From

/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands

to

https://docs.microsoft.com/en-us/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands

PR Summary

Fixes a broken link that 404's on GitHub but should direct to MS doc for Approved Verbs

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

[sdwheeler]

@andschwa The link is correct for the docs platform. It will be broken on GitHub but it is correct when published to the website. Please do not merge this PR.

See our contributor guide for more information: https://docs.microsoft.com/powershell/scripting/community/contributing/powershell-style-guide#hyperlinks

[sdwheeler]

Do not merge this change.

[rjmholt]

@JamesWTruher @bergmeister we should discuss how we handle this issue in general

[antoniouaa]

Maybe you should add an alternative link then? This was my first stop when searching for a list of approved verbs and it probably is for a lot of other people.

[sdwheeler]

This is source code, not documentation. You should be looking at the docs.microsoft.com site for documentation.

[andyleejordan]

I think people are still going to look at the GitHub repo for documentation too, especially since that's where it's been hosted for years.

[bergmeister]

Closing since PR #1738 superseded it. Please shout if that is not correct.