Documentation under reference/6 contains references to Windows PowerShell not to PowerShell Core

[it-praktyk]

Issue Details

Documentation under references/6/ contains references to Windows PowerShell not to PowerShell Core (or just PowerShell).

PS PowerShell-Docs/reference/6> Get-ChildItem -Recurse | Select-String 'Windows PowerShell' | Measure-Object -Line

Lines Words Characters Property
----- ----- ---------- --------
 2005          

Examples for the PowerShellGet module

PS PowerShell-Docs/reference/6/PowerShellGet> Get-ChildItem -Recurse | Select-String 'Windows PowerShell'

Find-DscResource.md:178:This follows standard wildcard character matching behavior for Windows PowerShell.
Find-Module.md:144:Per Windows PowerShell conventions, performs an OR search when you provide multiple arguments.
Find-Module.md:190:Returns only those modules that include specific kinds of Windows PowerShell functionality.
Find-Module.md:380:* This cmdlet runs on Windows PowerShell 3.0 or later releases of Windows PowerShell, on Windows 7 or Windows 2008 R2 and later releases of Windows.
Get-InstalledModule.md:24:The **Get-InstalledModule** cmdlet gets Windows PowerShell modules that are installed on a computer.
Install-Module.md:123:For example, if you try to install the ContosoServer module with a minimum version of 2.0, but the latest version of the ContosoServer module is 1.5, the **Install-Module** command does 
not install the ContosoServer module; it goes to install the next specified module, and Windows PowerShell display errors when the command is finished.
Install-Module.md:341:* This cmdlet runs on Windows PowerShell 3.0 or later releases of Windows PowerShell, on Windows 7 or Windows 2008 R2 and later releases of Windows.
Install-Module.md:355:  By default, modules are installed to the Program Files folder, to prevent confusion when you are installing Windows PowerShell Desired State Configuration (DSC) resources.You can pipe 
multiple **PSGetItemInfo** objects to **Install-Module**; this is another way of specifying multiple modules to install in a single command.
New-ScriptFileInfo.md:374:If the required modules are not in the global session state, Windows PowerShell imports them.
PowerShellGet.md:15:Windows PowerShell® is a task-based command-line shell and scripting language designed especially for system administration. This reference topic for the information technology (IT) 
professional provides assistance in utilizing the Windows PowerShell cmdlets to script and automate tasks.
Publish-Module.md:312:* This cmdlet runs on Windows PowerShell 3.0 or later releases of Windows PowerShell, on Windows 7 or Windows 2008 R2 and later releases of Windows.
Publish-Script.md:112:Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
Save-Module.md:122:Windows PowerShell does not interpret any characters that are enclosed in single quotation marks as escape sequences.
Save-Script.md:86:Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
Test-ScriptFileInfo.md:95:Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
Update-Module.md:25:The **Update-Module** cmdlet installs a newer version of a Windows PowerShell module that was installed from the online gallery by running Install-Module on the local computer.
Update-Module.md:229:* This cmdlet runs on Windows PowerShell 3.0 or later releases of Windows PowerShell, on Windows 7 or Windows 2008 R2 and later releases of Windows.
Update-ModuleManifest.md:239:When you import a module, Windows PowerShell runs the `Update-FormatData` cmdlet with the specified files.
Update-ModuleManifest.md:293:The HelpInfo XML file supports the Updatable Help feature that was introduced in Windows PowerShell version 3.0.
Update-ModuleManifest.md:453:Specifies the name of the Windows PowerShell host program that the module requires.
Update-ModuleManifest.md:454:Enter the name of the host program, such as Windows PowerShell ISE Host or ConsoleHost.
Update-ModuleManifest.md:472:Specifies the minimum version of the Windows PowerShell host program that works with the module.
Update-ModuleManifest.md:488:Specifies the minimum version of Windows PowerShell that will work with this module.
Update-ModuleManifest.md:575:Windows PowerShell loads the specified assemblies before updating types or formats, importing nested modules, or importing the module file that is specified in the value of the 
**RootModule** key.
Update-ModuleManifest.md:593:If the required modules are not in the global session state, Windows PowerShell imports them.
Update-ModuleManifest.md:618:Note: In Windows PowerShell 2.0, this key was called **ModuleToProcess**.
Update-ModuleManifest.md:668:When you import the module, Windows PowerShell runs the `Update-TypeData` cmdlet with the specified files.
Update-ScriptFileInfo.md:237:Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
Update-ScriptFileInfo.md:316:If the required modules are not in the global session state, Windows PowerShell imports them.

Version(s) of document impacted

• Impacts 6.1 document
• Impacts 6.0 document
• Impacts 5.1 document
• Impacts 5.0 document
• Impacts 4.0 document
• Impacts 3.0 document

Reason(s) for not selecting all version of documents

• The documented feature was introduced in selected version of PowerShell
• This issue only shows up in selected version of the document

[doctordns]

is this issue now resolved?

[it-praktyk]

Not exactly, still some usage of 'Windows PowerShell' should be reviewed, e.g. in examples usage of 'Windows PowerShell' should be corrected.

[bobbytreed]

These were cleaned up by #4330
Any new or additional instances can be opened as separate issues