Skip to content

style guide: formalize "Windows PowerShell" vs "PowerShell" #1228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zjalexander opened this issue May 22, 2017 · 1 comment
Closed

style guide: formalize "Windows PowerShell" vs "PowerShell" #1228

zjalexander opened this issue May 22, 2017 · 1 comment
Assignees

Comments

@zjalexander
Copy link
Contributor

from @joeyaiello:

Should "Windows PowerShell" ALWAYS get replaced with "PowerShell", even on old docs? In many cases, "Windows PowerShell" is the correct term, as that's the only kind of PowerShell where that version shipped, but if we think about "PowerShell" the platform, then something could have been "introduced in PowerShell 3.0".

The style guide should allow people to distinguish between using "Windows PowerShell" where it makes sense vs "PowerShell" which is the overall platform name.

Feedback is welcome on this issue, I'm honestly not sure about the best way to handle it.

@zjalexander zjalexander self-assigned this May 22, 2017
@pcgeek86
Copy link
Contributor

I'd recommend using the "PowerShell Desktop Edition" or "PowerShell Core Edition" where necessary, to keep consistent with the product development. Referring to PowerShell 1.0 through 5.1 would imply Desktop Edition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants