Replace Windows PowerShell with PowerShell (#2785)

Author: it-praktyk

reference/6/Microsoft.PowerShell.Management/Clear-Content.md

@@ -58,7 +58,7 @@ Using a filter to restrict the command to files with the .log file name extensio
 Type a user name, such as "User01" or "Domain01\User01", or enter a **PSCredential** object, such as one generated by the **Get-Credential** cmdlet.
 If you type a user name, you will be prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: String
@@ -79,7 +79,7 @@ The default is the current user.
 Type a user name, such as "User01" or "Domain01\User01", or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
 If you type a user name, you will be prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: PSCredential
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the *Path* parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -167,7 +167,7 @@ Specifies the paths to the items from which content is deleted.
 Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell having Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell having PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]
@@ -271,8 +271,8 @@ This cmdlet does not return any objects.
 For instance, `Clear-Content c:\mydir\*.txt`.
 If you include the parameter name, you can list the parameters in any order.
 
-  You can use **Clear-Content** with the Windows PowerShell FileSystem provider and with other providers that manipulate content.
-To clear items that are not considered to be content, such as items managed by the Windows PowerShell Certificate or Registry providers, use Clear-Item.
+  You can use **Clear-Content** with the PowerShell FileSystem provider and with other providers that manipulate content.
+To clear items that are not considered to be content, such as items managed by the PowerShell Certificate or Registry providers, use Clear-Item.
 
   The **Clear-Content** cmdlet is designed to work with the data exposed by any provider.
 To list the providers available in your session, type `Get-PsProvider`.

reference/6/Microsoft.PowerShell.Management/Clear-Item.md

@@ -30,7 +30,7 @@ Clear-Item -LiteralPath <String[]> [-Force] [-Filter <String>] [-Include <String
 ## DESCRIPTION
 The **Clear-Item** cmdlet clears the content of an item, but it does not delete the item.
 For example, the **Clear-Item** cmdlet can delete the value of a variable, but it does not delete the variable.
-The value that used to represent a cleared item is defined by each Windows PowerShell provider.
+The value that used to represent a cleared item is defined by each PowerShell provider.
 This cmdlet is similar to Clear-Content, but it works on aliases and variables, instead of files.
 
 ## EXAMPLES
@@ -45,9 +45,9 @@ PS Variable:\> Clear-Item TestVar1
 
 This command clears the value of the variable named TestVar1.
 The variable remains and is valid, but its value is set to null.
-The variable name is prefixed with Variable: to indicate the Windows PowerShell Variable provider.
+The variable name is prefixed with Variable: to indicate the PowerShell Variable provider.
 
-The alternate commands show that, to get the same result, you can switch to the Windows PowerShell Variable: drive and then run the **Clear-Item** command.
+The alternate commands show that, to get the same result, you can switch to the PowerShell Variable: drive and then run the **Clear-Item** command.
 
 ### Example 2: Clear all registry entries
 ```
@@ -69,7 +69,7 @@ The default is the current user.
 Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
 If you type a user name, you will be prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: PSCredential
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the *Path* parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -256,9 +256,9 @@ You can pipe a path string to this cmdlet.
 This cmdlet does not generate any output.
 
 ## NOTES
-* The **Clear-Item** cmdlet is supported only by several Windows PowerShell providers, including the Alias, Environment, Function, Registry, and Variable providers. As such, you can use **Clear-Item** to delete the content of items in the provider namespaces.
+* The **Clear-Item** cmdlet is supported only by several PowerShell providers, including the Alias, Environment, Function, Registry, and Variable providers. As such, you can use **Clear-Item** to delete the content of items in the provider namespaces.
 
-  You cannot use **Clear-Item** to delete the contents of a file, because the Windows PowerShell FileSystem provider does not support this cmdlet.
+  You cannot use **Clear-Item** to delete the contents of a file, because the PowerShell FileSystem provider does not support this cmdlet.
 To clear files, use the **Clear-Content**.
 
   You can also refer to **Clear-Item** by its built-in alias, cli.

reference/6/Microsoft.PowerShell.Management/Clear-ItemProperty.md

@@ -56,7 +56,7 @@ The default is the current user.
 Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
 If you type a user name, you will be prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: PSCredential
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the *Path* parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -146,7 +146,7 @@ Specifies the path to the property being cleared.
 Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]

reference/6/Microsoft.PowerShell.Management/Convert-Path.md

@@ -11,7 +11,7 @@ title:  Convert-Path
 # Convert-Path
 
 ## SYNOPSIS
-Converts a path from a Windows PowerShell path to a Windows PowerShell provider path.
+Converts a path from a PowerShell path to a PowerShell provider path.
 
 ## SYNTAX
 
@@ -26,7 +26,7 @@ Convert-Path -LiteralPath <String[]> [-UseTransaction] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-The **Convert-Path** cmdlet converts a path from a Windows PowerShell path to a Windows PowerShell provider path.
+The **Convert-Path** cmdlet converts a path from a PowerShell path to a PowerShell provider path.
 
 ## EXAMPLES
 
@@ -42,7 +42,7 @@ This command converts the current working directory, which is represented by a d
 PS C:\> Convert-Path HKLM:\Software\Microsoft
 ```
 
-This command converts the Windows PowerShell provider path to a standard registry path.
+This command converts the PowerShell provider path to a standard registry path.
 
 ### Example 3: Convert a path to a string
 ```
@@ -59,7 +59,7 @@ Specifies, as a string array, the path to be converted.
 The value of the *LiteralPath* parameter is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 ```
 
 ### -Path
-Specifies the Windows PowerShell path to be converted.
+Specifies the PowerShell path to be converted.
 
 ```yaml
 Type: String[]
@@ -121,7 +121,7 @@ You can pipe a path, but not a literal path, to this cmdlet.
 This cmdlet returns a string that contains the converted path.
 
 ## NOTES
-* The cmdlets that contain the Path noun manipulate path names and return the names in a concise format that all Windows PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators.
+* The cmdlets that contain the Path noun manipulate path names and return the names in a concise format that all PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators.
 
   You can use the path cmdlets with several providers, including the FileSystem, Registry, and Certificate providers.
 

reference/6/Microsoft.PowerShell.Management/Copy-Item.md

@@ -34,7 +34,7 @@ The **Copy-Item** cmdlet copies an item from one location to another location in
 For instance, it can copy a file to a folder, but it cannot copy a file to a certificate drive.
 
 This cmdlet does not cut or delete the items being copied.
-The particular items that the cmdlet can copy depend on the Windows PowerShell provider that exposes the item.
+The particular items that the cmdlet can copy depend on the PowerShell provider that exposes the item.
 For instance, it can copy files and directories in a file system drive and registry keys and entries in the registry drive.
 
 This cmdlet can copy and rename items in the same command.
@@ -180,7 +180,7 @@ The default is the current user.
 Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
 If you type a user name, you are prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: PSCredential
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the *Path* parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than have Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than have PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -279,7 +279,7 @@ Specifies a path to the item.
 The value of the *LiteralPath* parameter is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]

reference/6/Microsoft.PowerShell.Management/Copy-ItemProperty.md

@@ -51,7 +51,7 @@ The default is the current user.
 Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
 If you type a user name, you will be prompted for a password.
 
-This parameter is not supported by any providers installed with Windows PowerShell.
+This parameter is not supported by any providers installed with PowerShell.
 
 ```yaml
 Type: PSCredential
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the *Path* parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -149,7 +149,7 @@ Specifies a path to the item property.
 The value of the *LiteralPath* parameter is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]

reference/6/Microsoft.PowerShell.Management/Get-ChildItem.md

@@ -37,7 +37,7 @@ The `Get-ChildItem` cmdlet gets the items in one or more specified locations.
 If the item is a container, it gets the items inside the container, known as child items.
 You can use the `-Recurse` parameter to get items in all child containers and use the `-Depth` parameter to limit the number of levels to recurse.
 
-A location can be a file system location, such as a directory, or a location exposed by a different Windows PowerShell provider, such as a registry hive or a certificate store.
+A location can be a file system location, such as a directory, or a location exposed by a different PowerShell provider, such as a registry hive or a certificate store.
 
 ## Examples
 
@@ -61,7 +61,7 @@ Get-ChildItem -Path *.txt -Recurse -Force
 ```
 
 This command gets all of the .txt files in the current directory and its subdirectories.
-The `-Recurse` parameter directs Windows PowerShell to get objects recursively, and it indicates that the subject of the command is the specified directory and its contents.
+The `-Recurse` parameter directs PowerShell to get objects recursively, and it indicates that the subject of the command is the specified directory and its contents.
 The `-Force` parameter adds hidden files to the display.
 
 To use the `-Recurse` parameter on Windows PowerShell 2.0 and earlier versions of Windows PowerShell, the value use the `-Path` parameter must be a container.
@@ -101,7 +101,7 @@ Import-Module Microsoft.PowerShell.Security
 Get-ChildItem -Path Cert:\* -Recurse -CodeSigningCert
 ```
 
-This command gets all of the certificates in the Windows PowerShell Cert: drive that have code-signing authority.
+This command gets all of the certificates in the PowerShell Cert: drive that have code-signing authority.
 
 The first command imports the Microsoft.PowerShell.Security module into the session.
 This module includes the Certificate provider that creates the Cert: drive.
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -Depth
 
-This parameter, added in Powershell 5.0 enables you to control the depth of recursion.
+This parameter, added in Windows Powershell 5.0 enables you to control the depth of recursion.
 You use both the `-Recurse` and the `-Depth` parameter to limit the recursion.
 
 ```yaml
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 Specifies a filter in the provider's format or language.
 The value of this parameter qualifies the `-Path` parameter.
 The syntax of the filter, including the use of wildcards, depends on the provider.
-Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having Windows PowerShell filter the objects after they are retrieved.
+Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having PowerShell filter the objects after they are retrieved.
 
 ```yaml
 Type: String
@@ -373,7 +373,7 @@ Specifies a path to one or more locations.
 Unlike the `-Path` parameter, the value of the `-LiteralPath` parameter is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes escape characters, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences.
+Single quotation marks tell PowerShell not to interpret any characters as escape sequences.
 
 ```yaml
 Type: String[]