Merge pull request #2797 from it-praktyk/Correct_PowerShell_name_9

Replace Windows PowerShell with PowerShell - the Microsoft.PowerShell.Security module

Author: Sean Wheeler

reference/6/Microsoft.PowerShell.Security/ConvertTo-SecureString.md

@@ -65,7 +65,7 @@ The first command uses the *AsSecureString* parameter of the Read-Host cmdlet to
 After you enter the command, any characters that you type are converted into a secure string and then saved in the $Secure variable.
 
 The second command displays the contents of the $Secure variable.
-Because the $Secure variable contains a secure string, Windows PowerShell displays only the System.Security.SecureString type.
+Because the $Secure variable contains a secure string, PowerShell displays only the System.Security.SecureString type.
 
 The third command uses the ConvertFrom-SecureString cmdlet to convert the secure string in the $Secure variable into an encrypted standard string.
 It saves the result in the $Encrypted variable.

reference/6/Microsoft.PowerShell.Security/Get-Acl.md

@@ -61,14 +61,14 @@ This command gets the security descriptor of the C:Windows directory.
 Get-Acl C:\Windows\k*.log | Format-List -Property PSPath, Sddl
 ```
 
-This command gets the Windows PowerShell path and SDDL for all of the .log files in the C:\Windows
+This command gets the PowerShell path and SDDL for all of the .log files in the C:\Windows
 directory whose names begin with "k."
 
 The command uses the **Get-Acl** cmdlet to get objects representing the security descriptors of each log file.
 It uses a pipeline operator (|) to send the results to the Format-List cmdlet.
 The command uses the **Property** parameter of **Format-List** to display only the **PsPath** and **SDDL** properties of each security descriptor object.
 
-Lists are often used in Windows PowerShell, because long values appear truncated in tables.
+Lists are often used in PowerShell, because long values appear truncated in tables.
 
 The **SDDL** values are valuable to system administrators, because they are simple text strings
 that contain all of the information in the security descriptor. As such, they are easy to pass and
@@ -148,7 +148,7 @@ Accept wildcard characters: True
 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
-gettting the objects, rather than having Windows PowerShell filter the objects after they are
+gettting the objects, rather than having PowerShell filter the objects after they are
 retrieved.
 
 ```yaml

reference/6/Microsoft.PowerShell.Security/Get-AuthenticodeSignature.md

@@ -58,7 +58,7 @@ PS C:\> Get-ChildItem $pshome\*.* | ForEach-object {Get-AuthenticodeSignature $_
 ```
 
 This command lists all of the files in the $pshome directory that have a valid Authenticode signature.
-The $pshome automatic variable contains the path to the Windows PowerShell installation directory.
+The $pshome automatic variable contains the path to the PowerShell installation directory.
 
 The command uses the **Get-ChildItem** cmdlet to get the files in the $pshome directory.
 It uses a pattern of *.* to exclude directories (although it also excludes files without a dot in the filename).
@@ -91,7 +91,7 @@ Specifies the path to the file being examined.
 Unlike *FilePath*, the value of the *LiteralPath* parameter is used exactly as it is typed.
 No characters are interpreted as wildcards.
 If the path includes an escape character, enclose it in single quotation marks.
-Single quotation marks tell Windows PowerShell not to interpret any characters as escape characters.
+Single quotation marks tell PowerShell not to interpret any characters as escape characters.
 
 ```yaml
 Type: String[]
@@ -149,7 +149,7 @@ You can pipe a string that contains a file path to **Get-AuthenticodeSignature**
 **Get-AuthenticodeSignature** returns a signature object for each signature that it gets.
 
 ## NOTES
-* For information about Authenticode signatures in Windows PowerShell, see about_Signing.
+* For information about Authenticode signatures in PowerShell, see about_Signing.
 
 *
 

reference/6/Microsoft.PowerShell.Security/Get-ExecutionPolicy.md

@@ -22,7 +22,7 @@ Get-ExecutionPolicy [[-Scope] <ExecutionPolicyScope>] [-List] [<CommonParameters
 ## DESCRIPTION
 The **Get-ExecutionPolicy** cmdlet gets the execution policies for the current session.
 
-The execution policy is determined by execution policies that you set by using Set-ExecutionPolicy and the Group Policy settings for the Windows PowerShell execution policy.
+The execution policy is determined by execution policies that you set by using Set-ExecutionPolicy and the Group Policy settings for the PowerShell execution policy.
 The default value is Restricted.
 
 Without parameters, **Get-ExecutionPolicy** gets the execution policy that is effective in the session.
@@ -78,7 +78,7 @@ The second command gets only the effective execution policy, which is the one se
 PS C:\> Get-ExecutionPolicy
 RemoteSigned
 
-The second command shows what happens when you run a blocked script in a Windows PowerShell session in which the execution policy is RemoteSigned. The RemoteSigned policy prevents you from running scripts that are downloaded from the Internet unless they are digitally signed.
+The second command shows what happens when you run a blocked script in a PowerShell session in which the execution policy is RemoteSigned. The RemoteSigned policy prevents you from running scripts that are downloaded from the Internet unless they are digitally signed.
 PS C:\> .\Start-ActivityTracker.ps1
 .\Start-ActivityTracker.ps1 : File .\Start-ActivityTracker.ps1 cannot be loaded. The file .\Start-ActivityTracker.ps1 is not digitally signed. The script will not execute
 on the system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
@@ -91,7 +91,7 @@ At line:1 char:1
 The third command uses the Unblock-File cmdlet to unblock the script so it can run in the session.Before running an **Unblock-File** command, read the script contents and verify that it is safe.
 PS C:\> Unblock-File -Path "Start-ActivityTracker.ps1"
 
-This command shows the effect of the Unblock-File command. The command does not change the execution policy. However, it unblocks the script so that it runs in Windows PowerShell.
+This command shows the effect of the Unblock-File command. The command does not change the execution policy. However, it unblocks the script so that it runs in PowerShell.
 PS C:\> Get-ExecutionPolicy
 RemoteSigned
 PS C:\> Start-ActivityTracker.ps1
@@ -131,7 +131,7 @@ The execution policy set by a Group Policy for all users of the computer.
 - UserPolicy.
 The execution policy set by a Group Policy for the current user of the computer.
 - Process.
-The execution policy that is set for the current Windows PowerShell process.
+The execution policy that is set for the current PowerShell process.
 - CurrentUser.
 The execution policy that is set for the current user.
 - LocalMachine.
@@ -163,12 +163,12 @@ You cannot pipe input to this cmdlet.
 ### Microsoft.PowerShell.ExecutionPolicy
 
 ## NOTES
-* The execution policy is part of the security strategy of Windows PowerShell. It determines whether you can load configuration files (including your Windows PowerShell profile) and run scripts, and it determines which scripts, if any, must be digitally signed before they will run.
+* The execution policy is part of the security strategy of PowerShell. It determines whether you can load configuration files (including your PowerShell profile) and run scripts, and it determines which scripts, if any, must be digitally signed before they will run.
 
   The effective execution policy is determined by the policies that you set by using the Set-ExecutionPolicy cmdlet and the "Turn on Script Execution" group policies for computers and users.
 The precedence order is Computer Group Policy \> User Group Policy \> Process (session) execution policy \> User execution policy \> Computer execution policy.
 
-  For more information about Windows PowerShell execution policy, including definitions of the Windows PowerShell policies, see about_Execution_Policies (http://go.microsoft.com/fwlink/?LinkID=135170).
+  For more information about PowerShell execution policy, including definitions of the PowerShell policies, see about_Execution_Policies (http://go.microsoft.com/fwlink/?LinkID=135170).
 
 ## RELATED LINKS
 

reference/6/Microsoft.PowerShell.Security/Microsoft.PowerShell.Security.md

@@ -12,11 +12,11 @@ Module Name:  Microsoft.PowerShell.Security
 
 # Microsoft.PowerShell.Security Module
 ## Description
-This section contains the help topics for the cmdlets that are installed with Windows PowerShell Microsoft.PowerShell.Security module. The Security module contains cmdlets and providers that manage the basic security features of Windows.
+This section contains the help topics for the cmdlets that are installed with PowerShell Microsoft.PowerShell.Security module. The Security module contains cmdlets and providers that manage the basic security features of Windows.
 
 ## Microsoft.PowerShell.Security Cmdlets
 ### [Certificate-Provider](Providers/Certificate-Provider.md)
-Provides access to X.509 certificate stores and certificates in Windows PowerShell.
+Provides access to X.509 certificate stores and certificates in PowerShell.
 
 ### [ConvertFrom-SecureString](ConvertFrom-SecureString.md)
 Converts a secure string to an encrypted standard string.
@@ -35,7 +35,7 @@ Gets information about the Authenticode signature for a file.
 
 
 ### [Get-ChildItem-for-Certificate](Providers/et-ChildItem-for-Certificate.md)
-Gets certificate store locations, certificate stores, and certificates in the Windows PowerShell certificate store.
+Gets certificate store locations, certificate stores, and certificates in the PowerShell certificate store.
 
 ### [Get-Credential](Get-Credential.md)
 Gets a credential object based on a user name and password.
@@ -66,11 +66,11 @@ Changes the security descriptor of a specified item, such as a file or a registr
 
 
 ### [Set-AuthenticodeSignature](Set-AuthenticodeSignature.md)
-Adds an Authenticode signature to a Windows PowerShell script or other file.
+Adds an Authenticode signature to a PowerShell script or other file.
 
 
 ### [Set-ExecutionPolicy](Set-ExecutionPolicy.md)
-Changes the user preference for the Windows PowerShell execution policy.
+Changes the user preference for the PowerShell execution policy.
 
 
 ### [Test-FileCatalog](Test-FileCatalog.md)

reference/6/Microsoft.PowerShell.Security/Providers/Certificate-Provider.md

@@ -15,10 +15,10 @@ online version:  http://go.microsoft.com/fwlink/?LinkId=834968
  Cert:
 
 ## SHORT DESCRIPTION
- Provides access to X.509 certificate stores and certificates in Windows PowerShell.
+ Provides access to X.509 certificate stores and certificates in PowerShell.
 
 ## DETAILED DESCRIPTION
- The Windows PowerShell Certificate provider lets you navigate the certificate namespace and view the certificate stores and certificates. It also lets you open the Certificates snap-in for the Microsoft Management Console (MMC).
+ The PowerShell Certificate provider lets you navigate the certificate namespace and view the certificate stores and certificates. It also lets you open the Certificates snap-in for the Microsoft Management Console (MMC).
 
  NOTE: Beginning in Windows PowerShell 3.0, the Microsoft.PowerShell.Security module that contains the [Certificate Provider](Certificate-Provider.md) is not imported automatically into every session. To use the Cert: drive, use the [Import-Module](../../Microsoft.PowerShell.Core/Import-Module.md) cmdlet to import the module, or run a command that uses the Cert: drive, such as a "[Set-Location](../../Microsoft.PowerShell.Management/Set-Location.md) Cert:" command.
 
@@ -36,7 +36,7 @@ online version:  http://go.microsoft.com/fwlink/?LinkId=834968
 
  To populate the EnhancedKeyUsageList property, the Certificate provider copies the OID properties of the EnhancedKeyUsage (EKU) field in the certificate and creates a friendly name for it..
 
- The Certificate provider exposes the certificate namespace as the Cert: drive in Windows PowerShell. The Cert: drive has the following three levels:
+ The Certificate provider exposes the certificate namespace as the Cert: drive in PowerShell. The Cert: drive has the following three levels:
 
  --  Store locations (Microsoft.PowerShell.Commands.X509StoreLocation), which are high-level containers that group the certificates for the current user and for all users. Each system has a CurrentUser and LocalMachine (all users) store location.
 
@@ -48,7 +48,7 @@ online version:  http://go.microsoft.com/fwlink/?LinkId=834968
 
  In Windows PowerShell 2.0, the Certificate provider supports the [Get-Location](../../Microsoft.PowerShell.Management/Get-Location.md), [Set-Location](../../Microsoft.PowerShell.Management/Set-Location.md), [Get-Item](../../Microsoft.PowerShell.Management/Get-Item.md), [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md), and [Invoke-Item](../../Microsoft.PowerShell.Management/Invoke-Item.md) cmdlets.
 
- In addition, Windows PowerShell Security module (Microsoft.PowerShell.Security), which includes the Certificate provider, also includes cmdlets to get and set Authenticode signatures and to get certificates. For a list of cmdlets in the Security module, type "[Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md) -module *security".
+ In addition, PowerShell Security module (Microsoft.PowerShell.Security), which includes the Certificate provider, also includes cmdlets to get and set Authenticode signatures and to get certificates. For a list of cmdlets in the Security module, type "[Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md) -module *security".
 
 ## CAPABILITIES
  ShouldProcess
@@ -228,7 +228,7 @@ Remove-Item -Path cert:\LocalMachine\CA\5DDC44652E62BF9AA1116DC41DE44AB47C87BDD0
 
  The first command uses the Enable-WSManCredSSP cmdlet to enable Credential Security Service Provider (CredSSP) authentication on a client on the S1 remote computer. CredSSP permits delegated authentication.
 
- The second command uses the Connect-WSMan cmdlet to connect the S1 computer to the WinRM service on the local computer. When this command completes, the S1 computer appears in the local WSMan: drive in Windows PowerShell.
+ The second command uses the Connect-WSMan cmdlet to connect the S1 computer to the WinRM service on the local computer. When this command completes, the S1 computer appears in the local WSMan: drive in PowerShell.
 
  The third command uses the Set-Item cmdlet in the WSMan: drive to enable the CredSSP attribute for the WinRM service.
 
@@ -328,7 +328,7 @@ Remove-Item -path cert:\LocalMachine\*test* -Recurse
 ```
 
 ## DYNAMIC PARAMETERS
- Dynamic parameters are cmdlet parameters that are added by a Windows PowerShell provider and are available only when the cmdlet is being used in the provider-enabled drive.
+ Dynamic parameters are cmdlet parameters that are added by a PowerShell provider and are available only when the cmdlet is being used in the provider-enabled drive.
 
 ### CodeSigningCert <System.Management.Automation.SwitchParameter>
  Gets only those certificates with code-signing authority.

reference/6/Microsoft.PowerShell.Security/Providers/get-childitem-for-certificate.md

@@ -18,7 +18,7 @@ Get-ChildItem [-CodeSigningCert] [-DnsName <string>] [-EKU <string>] [-ExpiringI
 ```
 
 ## Description
- In the Cert: drive, the [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md) cmdlet gets certificate store locations, certificate stores, and certificates. The Windows PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to Windows PowerShell.
+ In the Cert: drive, the [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md) cmdlet gets certificate store locations, certificate stores, and certificates. The PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to PowerShell.
 
  Beginning in Windows PowerShell 3.0, the Certificate provider enhances its support for managing Secure Socket Layer (SSL) certificates for web hosting. New filtering parameters, DnsName, EKU, ,ExpiringInDays, and SSLServerAuthentication have been added to [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md) to enable you to search for certificates based on their DNS names and expiration dates, and distinguish client and server authentication certificates by the value of their Enhanced Key Usage (EKU) properties. The new dynamic parameters work in Windows PowerShell 3.0 and newer releases of Windows PowerShell, running on Windows 8, Windows Server 2012 and newer releases of the Windows operating system.
 
@@ -263,7 +263,7 @@ C:\PS>Get-ChildItem -Path cert: -CodeSigningCert -Recurse
 
 Description
 -----------
-This command uses the CodeSigningCert and Recurse parameters of the Get-ChildItem cmdlet to get all of the certificates on the computer that have code-signing authority. Because the full path is specified, this command can be run in any Windows PowerShell drive.
+This command uses the CodeSigningCert and Recurse parameters of the Get-ChildItem cmdlet to get all of the certificates on the computer that have code-signing authority. Because the full path is specified, this command can be run in any PowerShell drive.
 
 ```
 

reference/6/Microsoft.PowerShell.Security/Providers/move-item-for-certificate.md

@@ -18,7 +18,7 @@ Move-Item [-Path] <string[]> [[-Destination] <string>] [-Confirm] [-WhatIf] [<Co
 ```
 
 ## Description
- In the Cert: drive, [Move-Item](../../Microsoft.PowerShell.Management/Move-Item.md) moves certificates from one certificate store to another certificate store. The Windows PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to Windows PowerShell.
+ In the Cert: drive, [Move-Item](../../Microsoft.PowerShell.Management/Move-Item.md) moves certificates from one certificate store to another certificate store. The PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to PowerShell.
 
  Beginning in Windows PowerShell 3.0, the Certificate provider enhances its support for managing Secure Socket Layer (SSL) certificates for web hosting by enabling you to use the [Move-Item](../../Microsoft.PowerShell.Management/Move-Item.md) cmdlet to move certificates between certificate stores.  You cannot use this feature to move a certificate to a different certificate store location, such as a move from LocalMachine to CurrentUser, or to move certificate stores. Also, [Move-Item](../../Microsoft.PowerShell.Management/Move-Item.md) does not move private keys.
 
@@ -97,7 +97,7 @@ Description
 -----------
 This command uses the Move-Item cmdlet to move a certificate from the My store to the WebHosting store.
 
-Because the command uses absolute paths, you can run it from any Windows PowerShell drive. You can also run it from a Cert: drive path and use relative paths.
+Because the command uses absolute paths, you can run it from any PowerShell drive. You can also run it from a Cert: drive path and use relative paths.
 
 ```
 

reference/6/Microsoft.PowerShell.Security/Providers/new-item-for-certificate.md

@@ -20,7 +20,7 @@ New-Item [-Path] <string[]> [-Confirm] [-WhatIf] [<CommonParameters>]
 ```
 
 ## Description
- In the Cert: drive, the [New-Item](../../Microsoft.PowerShell.Management/New-Item.md) cmdlet creates new certificate stores in the LocalMachine certificate store location. The Windows PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to Windows PowerShell.
+ In the Cert: drive, the [New-Item](../../Microsoft.PowerShell.Management/New-Item.md) cmdlet creates new certificate stores in the LocalMachine certificate store location. The PowerShell [Certificate Provider](Certificate-Provider.md) adds the Cert: drive to PowerShell.
 
  Beginning in Windows PowerShell 3.0, the Certificate provider enables you to use the [New-Item](../../Microsoft.PowerShell.Management/New-Item.md) cmdlet to create new certificate stores. You can also use the [Remove-Item](../../Microsoft.PowerShell.Management/Remove-Item.md) cmdlet to delete the certificate stores that you create.  You cannot use the [New-Item](../../Microsoft.PowerShell.Management/New-Item.md) cmdlet to create certificates or certificate store locations, or to create certificate stores in the CurrentUser certficate store location.