Replace Windows PowerShell with PowerShell - the Microsoft.PowerShell.Core - 1

reference/6/Microsoft.PowerShell.Core/About/about_Arrays.md

@@ -43,7 +43,7 @@ $B = 5..8
 
 As a result, $B contains four values: 5, 6, 7, and 8.
 
-When no data type is specified, Windows PowerShell creates each array as an
+When no data type is specified, PowerShell creates each array as an
 object array (type: System.Object[]). To determine the data type of an array,
 use the GetType() method. For example, to determine the data type of the $a
 array, type:
@@ -689,7 +689,7 @@ Stopped  AppIDSvc           Application Identity
 To get the properties and methods of an array, such as the Length property and
 the SetValue method, use the InputObject parameter of the Get-Member cmdlet.
 
-When you pipe an array to `Get-Member`, Windows PowerShell sends the items one
+When you pipe an array to `Get-Member`, PowerShell sends the items one
 at a time and Get-Member returns the type of each item in the array (ignoring
 duplicates).
 

reference/6/Microsoft.PowerShell.Core/About/about_Assignment_Operators.md

@@ -16,7 +16,7 @@ Describes how to use operators to assign values to variables.
 Assignment operators assign one or more values to a variable. They can
 perform numeric operations on the values before the assignment.
 
-Windows PowerShell supports the following assignment operators.
+PowerShell supports the following assignment operators.
 
 |Operator|Description                                                  |
 |--------|-------------------------------------------------------------|
@@ -60,14 +60,14 @@ replace the existing value of the variable, or you can append a new value
 to the existing value.
 
 The basic assignment operator is the equal sign `=` `(ASCII 61)`. For
-example, the following statement assigns the value Windows PowerShell to
+example, the following statement assigns the value PowerShell to
 the $MyShell variable:
 
 ```powershell
-$MyShell = "Windows PowerShell"
+$MyShell = "PowerShell"
 ```
 
-When you assign a value to a variable in Windows PowerShell, the variable
+When you assign a value to a variable in PowerShell, the variable
 is created if it did not already exist. For example, the first of the
 following two assignement statements creates the $a variable and assigns a
 value of 6 to $a. The second assignment statement assigns a value of 12 to
@@ -79,7 +79,7 @@ $a = 6
 $a = 12
 ```
 
-Variables in Windows PowerShell do not have a specific data type unless you
+Variables in PowerShell do not have a specific data type unless you
 cast them. When a variable contains only one object, the variable takes the
 data type of that object. When a variable contains a collection of objects,
 the variable has the System.Object data type. Therefore, you can assign any
@@ -142,7 +142,7 @@ $a = "apple", "orange", "lemon", "grape"
 ```
 
 To assign a hash table to a variable, use the standard hash table notation
-in Windows PowerShell. Type an at sign `@` followed by key/value pairs that
+in PowerShell. Type an at sign `@` followed by key/value pairs that
 are separated by semicolons `;` and enclosed in braces `{ }`. For example,
 to assign a hash table to the $a variable, type:
 
@@ -151,7 +151,7 @@ $a = @{one=1; two=2; three=3}
 ```
 
 To assign hexadecimal values to a variable, precede the value with `0x`.
-Windows PowerShell converts the hexadecimal value (0x10) to a decimal value
+PowerShell converts the hexadecimal value (0x10) to a decimal value
 (in this case, 16) and assigns that value to the $a variable. For example,
 to assign a value of 0x10 to the $a variable, type:
 
@@ -167,7 +167,7 @@ assign a value of 3.1415 to the power of 1,000 to the $a variable, type:
 $a = 3.1415e3
 ```
 
-Windows PowerShell can also convert kilobytes `KB`, megabytes `MB`, and
+PowerShell can also convert kilobytes `KB`, megabytes `MB`, and
 gigabytes `GB` into bytes. For example, to assign a value of 10 kilobytes
 to the $a variable, type:
 
@@ -217,7 +217,7 @@ $a
 ```
 
 ```
-Windows PowerShell
+PowerShell
 ```
 
 When the value of the variable is an array, the `+=` operator appends the
@@ -412,7 +412,7 @@ $a *= 2
 $a = ($a * 2)
 ```
 
-When a variable contains a string value, Windows PowerShell appends the
+When a variable contains a string value, PowerShell appends the
 specified number of strings to the value, as follows:
 
 ```powershell
@@ -690,7 +690,7 @@ $a
 file3
 ```
 
-If the first value is an integer, Windows PowerShell treats all operations
+If the first value is an integer, PowerShell treats all operations
 as integer operations and casts new values to integers. This occurs in the
 following example:
 
@@ -754,7 +754,7 @@ In addition, when you precede a variable name with a data type, the type of
 that variable is locked unless you explicitly override the type by
 specifying another data type. If you try to assign a value that is
 incompatible with the existing type, and you do not explicitly override the
-type, Windows PowerShell displays an error, as shown in the following
+type, PowerShell displays an error, as shown in the following
 example:
 
 ```powershell
@@ -775,7 +775,7 @@ At line:1 char:3
 [string]$a = "string"
 ```
 
-In Windows PowerShell, the data types of variables that contain multiple
+In PowerShell, the data types of variables that contain multiple
 items in an array are handled differently from the data types of variables
 that contain a single item. Unless a data type is specifically assigned to
 an array variable, the data type is always `System.Object []`. This data
@@ -789,7 +789,7 @@ array type:
 [string []] $a = "one", "two", "three"
 ```
 
-Windows PowerShell variables can be any .NET Framework data type. In
+PowerShell variables can be any .NET Framework data type. In
 addition, you can assign any fully qualified .NET Framework data type that
 is available in the current process. For example, the following command
 specifies a `System.DateTime` data type:
@@ -808,7 +808,7 @@ Tuesday, May 31, 2005 12:00:00 AM
 
 # ASSIGNING MULTIPLE VARIABLES
 
-In Windows PowerShell, you can assign values to multiple variables by using
+In PowerShell, you can assign values to multiple variables by using
 a single command. The first element of the assignment value is assigned to
 the first variable, the second element is assigned to the second variable,
 the third element to the third variable, and so on. For example, the
@@ -827,7 +827,7 @@ following command contains three variables and five values:
 $a, $b, $c = 1, 2, 3, 4, 5
 ```
 
-Therefore, Windows PowerShell assigns the value 1 to the $a variable and
+Therefore, PowerShell assigns the value 1 to the $a variable and
 the value 2 to the $b variable. It assigns the values 3, 4, and 5 to the $c
 variable. To assign the values in the $c variable to three other variables,
 use the following format:

reference/6/Microsoft.PowerShell.Core/About/about_Classes.md

@@ -19,8 +19,8 @@ Starting in PowerShell 5.0, PowerShell adds language
 for defining classes and other user-defined types, by using formal syntax
 and semantics that are similar to other object-oriented programming
 languages. The goal is to enable developers and IT professionals to
-embrace Windows PowerShell for a wider range of use cases, simplify
-development of Windows PowerShell artifacts and accelerate coverage
+embrace PowerShell for a wider range of use cases, simplify
+development of PowerShell artifacts and accelerate coverage
 of management surfaces.
 
 A class declaration is like a blueprint that is used to create instances or
@@ -33,10 +33,10 @@ and each instance can have different values in its properties.
 
 ## SUPPORTED SCENARIOS
 
-- Define custom types in Windows PowerShell by using familiar object-oriented
+- Define custom types in PowerShell by using familiar object-oriented
   programming constructs, such as classes, properties, methods, inheritance,
   etc.
-- Debug types by using the Windows PowerShell language.
+- Debug types by using the PowerShell language.
 - Generate and handle exceptions by using formal mechanisms, and at the right
   level.
 - Define DSC resources and their associated types by using the PowerShell

reference/6/Microsoft.PowerShell.Core/About/about_Command_Precedence.md

@@ -20,7 +20,7 @@ to avoid command-name conflicts in your session.
 
 ## COMMAND PRECEDENCE
 
-When a session includes commands that have the same name, Windows PowerShell
+When a session includes commands that have the same name, PowerShell
 uses the following rules to decide which command to run.
 
 These rules become very important when you add commands to your session from

reference/6/Microsoft.PowerShell.Core/About/about_Command_Syntax.md

@@ -9,7 +9,7 @@ title:  about_Command_Syntax
 
 # SHORT DESCRIPTION
 
-Describes the syntax diagrams that are used in Windows PowerShell.
+Describes the syntax diagrams that are used in PowerShell.
 
 # LONG DESCRIPTION
 
@@ -26,7 +26,7 @@ command.
 To construct a command, follow the syntax diagram from left to right. Select
 from among the optional parameters and provide values for the placeholders.
 
-Windows PowerShell uses the following notation for syntax diagrams.
+PowerShell uses the following notation for syntax diagrams.
 
 ```powershell
 <command-name> -<Required Parameter Name> <Required Parameter Value>
@@ -44,7 +44,7 @@ New-Alias [-Name] <string> [-Value] <string> [-Description <string>]
 [-PassThru] [-Scope <string>] [-Confirm] [-WhatIf] [<CommonParameters>]
 ```
 
-The syntax is capitalized for readability, but Windows PowerShell is
+The syntax is capitalized for readability, but PowerShell is
 case-insensitive.
 
 The syntax diagram has the following elements.
@@ -63,8 +63,8 @@ For example, the `Get-Help` command has a **Name** parameter that lets you
 specify the name of the topic for which help is displayed. The topic name is
 the value of the **Name** parameter.
 
-In a Windows PowerShell command, parameter names always begin with a hyphen.
-The hyphen tells Windows PowerShell that the item in the command is a
+In a PowerShell command, parameter names always begin with a hyphen.
+The hyphen tells PowerShell that the item in the command is a
 parameter name.
 
 For example, to use the Name parameter of `New-Alias`, you type the following:
@@ -167,7 +167,7 @@ returns a random number.
 
 In each parameter set, the parameters appear in position order. The order of
 parameters in a command matters only when you omit the optional parameter
-names. When parameter names are omitted, Windows PowerShell assigns values to
+names. When parameter names are omitted, PowerShell assigns values to
 parameters by position and type. For more information about parameter
 position, see `about_Parameters`.
 

reference/6/Microsoft.PowerShell.Core/About/about_Comment_Based_Help.md

@@ -842,7 +842,7 @@ Get-Help
 
 SYNOPSIS
 
-Displays information about Windows PowerShell cmdlets and concepts.
+Displays information about PowerShell cmdlets and concepts.
 ...
 ```
 

reference/6/Microsoft.PowerShell.Core/About/about_CommonParameters.md

@@ -15,7 +15,7 @@ Describes the parameters that can be used with any cmdlet.
 ## LONG DESCRIPTION
 
 The common parameters are a set of cmdlet parameters that you can use with any
-cmdlet. They are implemented by Windows PowerShell, not by the cmdlet
+cmdlet. They are implemented by PowerShell, not by the cmdlet
 developer, and they are automatically available to any cmdlet.
 
 You can use the common parameters with any cmdlet, but they might not have an
@@ -26,7 +26,7 @@ The common parameters are also available on advanced functions that use the
 CmdletBinding attribute or the Parameter attribute, and on all workflows.
 
 Several common parameters override system defaults or preferences that you set
-by using the Windows PowerShell preference variables. Unlike the preference
+by using the PowerShell preference variables. Unlike the preference
 variables, the common parameters affect only the commands in which they are
 used.
 
@@ -114,7 +114,7 @@ Valid values:
 
 - Stop. Displays the error message and stops executing the command.
 
-- Suspend. This value is only available in Windows PowerShell workflows. When
+- Suspend. This value is only available in PowerShell workflows. When
   a workflow runs into terminating error, this action preference automatically
   suspends the job to allow for further investigation. After investigation,
   the workflow can be resumed.
@@ -215,7 +215,7 @@ are sent through the pipeline. If you omit this parameter, objects are sent as
 they are generated.
 
 This resource management parameter is designed for advanced users. When you
-use this parameter, Windows PowerShell does not call the next cmdlet in the
+use this parameter, PowerShell does not call the next cmdlet in the
 pipeline until the number of objects generated equals OutBuffer + 1.
 Thereafter, it sends all objects as they are generated.
 
@@ -413,7 +413,7 @@ command:
 PS> Remove-Item Date.csv -WhatIf
 ```
 
-Instead of removing the item, Windows PowerShell lists the operations it would
+Instead of removing the item, PowerShell lists the operations it would
 perform and the items that would be affected. This command produces the
 following output:
 
@@ -445,7 +445,7 @@ Valid values:
   risk of the cmdlet.
 
 For example, the following command uses the Confirm parameter with a
-Remove-Item command. Before removing the item, Windows PowerShell lists the
+Remove-Item command. Before removing the item, PowerShell lists the
 operations it would perform and the items that would be affected, and asks for
 approval.
 

reference/6/Microsoft.PowerShell.Core/About/about_Core_Commands.md

@@ -15,7 +15,7 @@ Lists the cmdlets that are designed for use with PowerShell providers.
 ## LONG DESCRIPTION
 
 PowerShell includes a set of cmdlets that are specifically designed to manage
-the items in the data stores that are exposed by Windows PowerShell providers.
+the items in the data stores that are exposed by PowerShell providers.
 You can use these cmdlets in the same ways to manage all the different types
 of data that the providers make available to you. For more information about
 providers, type "get-help about_providers".

reference/6/Microsoft.PowerShell.Core/About/about_Data_Sections.md

@@ -17,7 +17,7 @@ data from script logic.
 
 ### Long Description
 
-Scripts that are designed for Windows PowerShell can have one or more
+Scripts that are designed for PowerShell can have one or more
 Data sections that contain only data. You can include one or more Data
 sections in any script, function, or advanced function. The content of
 the Data section is restricted to a specified subset of the Windows
@@ -28,7 +28,7 @@ both logic and data. It lets you have separate string resource files for
 text, such as error messages and Help strings. It also isolates the code
 logic, which facilitates security and validation tests.
 
-In Windows PowerShell, the Data section is used to support script
+In PowerShell, the Data section is used to support script
 internationalization. You can use Data sections to make it easier to
 isolate, locate, and process strings that will be translated into many
 user interface (UI) languages.
@@ -49,7 +49,7 @@ The Data keyword is required. It is not case-sensitive.
 
 The permitted content is limited to the following elements:
 
-- All Windows PowerShell operators, except `-match`
+- All PowerShell operators, except `-match`
 
 - `If`, `Else`, and `ElseIf` statements
 
@@ -159,7 +159,7 @@ Simple data strings.
 
 ```powershell
 DATA {
-    "Thank you for using my Windows PowerShell Organize.pst script."
+    "Thank you for using my PowerShell Organize.pst script."
     "It is provided free of charge to the community."
     "I appreciate your comments and feedback."
 }