Skip to content

Commit d681723

Browse files
it-praktykSean Wheeler
authored and
Sean Wheeler
committed
Replace Windows PowerShell with PowerShell (#2813)
1 parent 6ea786a commit d681723

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+415
-414
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ $B = 5..8
4343

4444
As a result, $B contains four values: 5, 6, 7, and 8.
4545

46-
When no data type is specified, Windows PowerShell creates each array as an
46+
When no data type is specified, PowerShell creates each array as an
4747
object array (type: System.Object[]). To determine the data type of an array,
4848
use the GetType() method. For example, to determine the data type of the $a
4949
array, type:
@@ -689,7 +689,7 @@ Stopped AppIDSvc Application Identity
689689
To get the properties and methods of an array, such as the Length property and
690690
the SetValue method, use the InputObject parameter of the Get-Member cmdlet.
691691

692-
When you pipe an array to `Get-Member`, Windows PowerShell sends the items one
692+
When you pipe an array to `Get-Member`, PowerShell sends the items one
693693
at a time and Get-Member returns the type of each item in the array (ignoring
694694
duplicates).
695695

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

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Describes how to use operators to assign values to variables.
1616
Assignment operators assign one or more values to a variable. They can
1717
perform numeric operations on the values before the assignment.
1818

19-
Windows PowerShell supports the following assignment operators.
19+
PowerShell supports the following assignment operators.
2020

2121
|Operator|Description |
2222
|--------|-------------------------------------------------------------|
@@ -60,14 +60,14 @@ replace the existing value of the variable, or you can append a new value
6060
to the existing value.
6161

6262
The basic assignment operator is the equal sign `=` `(ASCII 61)`. For
63-
example, the following statement assigns the value Windows PowerShell to
63+
example, the following statement assigns the value PowerShell to
6464
the $MyShell variable:
6565

6666
```powershell
67-
$MyShell = "Windows PowerShell"
67+
$MyShell = "PowerShell"
6868
```
6969

70-
When you assign a value to a variable in Windows PowerShell, the variable
70+
When you assign a value to a variable in PowerShell, the variable
7171
is created if it did not already exist. For example, the first of the
7272
following two assignement statements creates the $a variable and assigns a
7373
value of 6 to $a. The second assignment statement assigns a value of 12 to
@@ -79,7 +79,7 @@ $a = 6
7979
$a = 12
8080
```
8181

82-
Variables in Windows PowerShell do not have a specific data type unless you
82+
Variables in PowerShell do not have a specific data type unless you
8383
cast them. When a variable contains only one object, the variable takes the
8484
data type of that object. When a variable contains a collection of objects,
8585
the variable has the System.Object data type. Therefore, you can assign any
@@ -142,7 +142,7 @@ $a = "apple", "orange", "lemon", "grape"
142142
```
143143

144144
To assign a hash table to a variable, use the standard hash table notation
145-
in Windows PowerShell. Type an at sign `@` followed by key/value pairs that
145+
in PowerShell. Type an at sign `@` followed by key/value pairs that
146146
are separated by semicolons `;` and enclosed in braces `{ }`. For example,
147147
to assign a hash table to the $a variable, type:
148148

@@ -151,7 +151,7 @@ $a = @{one=1; two=2; three=3}
151151
```
152152

153153
To assign hexadecimal values to a variable, precede the value with `0x`.
154-
Windows PowerShell converts the hexadecimal value (0x10) to a decimal value
154+
PowerShell converts the hexadecimal value (0x10) to a decimal value
155155
(in this case, 16) and assigns that value to the $a variable. For example,
156156
to assign a value of 0x10 to the $a variable, type:
157157

@@ -167,7 +167,7 @@ assign a value of 3.1415 to the power of 1,000 to the $a variable, type:
167167
$a = 3.1415e3
168168
```
169169

170-
Windows PowerShell can also convert kilobytes `KB`, megabytes `MB`, and
170+
PowerShell can also convert kilobytes `KB`, megabytes `MB`, and
171171
gigabytes `GB` into bytes. For example, to assign a value of 10 kilobytes
172172
to the $a variable, type:
173173

@@ -217,7 +217,7 @@ $a
217217
```
218218

219219
```
220-
Windows PowerShell
220+
PowerShell
221221
```
222222

223223
When the value of the variable is an array, the `+=` operator appends the
@@ -412,7 +412,7 @@ $a *= 2
412412
$a = ($a * 2)
413413
```
414414

415-
When a variable contains a string value, Windows PowerShell appends the
415+
When a variable contains a string value, PowerShell appends the
416416
specified number of strings to the value, as follows:
417417

418418
```powershell
@@ -690,7 +690,7 @@ $a
690690
file3
691691
```
692692

693-
If the first value is an integer, Windows PowerShell treats all operations
693+
If the first value is an integer, PowerShell treats all operations
694694
as integer operations and casts new values to integers. This occurs in the
695695
following example:
696696

@@ -754,7 +754,7 @@ In addition, when you precede a variable name with a data type, the type of
754754
that variable is locked unless you explicitly override the type by
755755
specifying another data type. If you try to assign a value that is
756756
incompatible with the existing type, and you do not explicitly override the
757-
type, Windows PowerShell displays an error, as shown in the following
757+
type, PowerShell displays an error, as shown in the following
758758
example:
759759

760760
```powershell
@@ -775,7 +775,7 @@ At line:1 char:3
775775
[string]$a = "string"
776776
```
777777

778-
In Windows PowerShell, the data types of variables that contain multiple
778+
In PowerShell, the data types of variables that contain multiple
779779
items in an array are handled differently from the data types of variables
780780
that contain a single item. Unless a data type is specifically assigned to
781781
an array variable, the data type is always `System.Object []`. This data
@@ -789,7 +789,7 @@ array type:
789789
[string []] $a = "one", "two", "three"
790790
```
791791

792-
Windows PowerShell variables can be any .NET Framework data type. In
792+
PowerShell variables can be any .NET Framework data type. In
793793
addition, you can assign any fully qualified .NET Framework data type that
794794
is available in the current process. For example, the following command
795795
specifies a `System.DateTime` data type:
@@ -808,7 +808,7 @@ Tuesday, May 31, 2005 12:00:00 AM
808808

809809
# ASSIGNING MULTIPLE VARIABLES
810810

811-
In Windows PowerShell, you can assign values to multiple variables by using
811+
In PowerShell, you can assign values to multiple variables by using
812812
a single command. The first element of the assignment value is assigned to
813813
the first variable, the second element is assigned to the second variable,
814814
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:
827827
$a, $b, $c = 1, 2, 3, 4, 5
828828
```
829829

830-
Therefore, Windows PowerShell assigns the value 1 to the $a variable and
830+
Therefore, PowerShell assigns the value 1 to the $a variable and
831831
the value 2 to the $b variable. It assigns the values 3, 4, and 5 to the $c
832832
variable. To assign the values in the $c variable to three other variables,
833833
use the following format:

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@ Starting in PowerShell 5.0, PowerShell adds language
1919
for defining classes and other user-defined types, by using formal syntax
2020
and semantics that are similar to other object-oriented programming
2121
languages. The goal is to enable developers and IT professionals to
22-
embrace Windows PowerShell for a wider range of use cases, simplify
23-
development of Windows PowerShell artifacts and accelerate coverage
22+
embrace PowerShell for a wider range of use cases, simplify
23+
development of PowerShell artifacts and accelerate coverage
2424
of management surfaces.
2525

2626
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.
3333

3434
## SUPPORTED SCENARIOS
3535

36-
- Define custom types in Windows PowerShell by using familiar object-oriented
36+
- Define custom types in PowerShell by using familiar object-oriented
3737
programming constructs, such as classes, properties, methods, inheritance,
3838
etc.
39-
- Debug types by using the Windows PowerShell language.
39+
- Debug types by using the PowerShell language.
4040
- Generate and handle exceptions by using formal mechanisms, and at the right
4141
level.
4242
- Define DSC resources and their associated types by using the PowerShell

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ to avoid command-name conflicts in your session.
2020

2121
## COMMAND PRECEDENCE
2222

23-
When a session includes commands that have the same name, Windows PowerShell
23+
When a session includes commands that have the same name, PowerShell
2424
uses the following rules to decide which command to run.
2525

2626
These rules become very important when you add commands to your session from

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ title: about_Command_Syntax
99

1010
# SHORT DESCRIPTION
1111

12-
Describes the syntax diagrams that are used in Windows PowerShell.
12+
Describes the syntax diagrams that are used in PowerShell.
1313

1414
# LONG DESCRIPTION
1515

@@ -26,7 +26,7 @@ command.
2626
To construct a command, follow the syntax diagram from left to right. Select
2727
from among the optional parameters and provide values for the placeholders.
2828

29-
Windows PowerShell uses the following notation for syntax diagrams.
29+
PowerShell uses the following notation for syntax diagrams.
3030

3131
```powershell
3232
<command-name> -<Required Parameter Name> <Required Parameter Value>
@@ -44,7 +44,7 @@ New-Alias [-Name] <string> [-Value] <string> [-Description <string>]
4444
[-PassThru] [-Scope <string>] [-Confirm] [-WhatIf] [<CommonParameters>]
4545
```
4646

47-
The syntax is capitalized for readability, but Windows PowerShell is
47+
The syntax is capitalized for readability, but PowerShell is
4848
case-insensitive.
4949

5050
The syntax diagram has the following elements.
@@ -63,8 +63,8 @@ For example, the `Get-Help` command has a **Name** parameter that lets you
6363
specify the name of the topic for which help is displayed. The topic name is
6464
the value of the **Name** parameter.
6565

66-
In a Windows PowerShell command, parameter names always begin with a hyphen.
67-
The hyphen tells Windows PowerShell that the item in the command is a
66+
In a PowerShell command, parameter names always begin with a hyphen.
67+
The hyphen tells PowerShell that the item in the command is a
6868
parameter name.
6969

7070
For example, to use the Name parameter of `New-Alias`, you type the following:
@@ -167,7 +167,7 @@ returns a random number.
167167

168168
In each parameter set, the parameters appear in position order. The order of
169169
parameters in a command matters only when you omit the optional parameter
170-
names. When parameter names are omitted, Windows PowerShell assigns values to
170+
names. When parameter names are omitted, PowerShell assigns values to
171171
parameters by position and type. For more information about parameter
172172
position, see `about_Parameters`.
173173

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -842,7 +842,7 @@ Get-Help
842842
843843
SYNOPSIS
844844
845-
Displays information about Windows PowerShell cmdlets and concepts.
845+
Displays information about PowerShell cmdlets and concepts.
846846
...
847847
```
848848

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Describes the parameters that can be used with any cmdlet.
1515
## LONG DESCRIPTION
1616

1717
The common parameters are a set of cmdlet parameters that you can use with any
18-
cmdlet. They are implemented by Windows PowerShell, not by the cmdlet
18+
cmdlet. They are implemented by PowerShell, not by the cmdlet
1919
developer, and they are automatically available to any cmdlet.
2020

2121
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
2626
CmdletBinding attribute or the Parameter attribute, and on all workflows.
2727

2828
Several common parameters override system defaults or preferences that you set
29-
by using the Windows PowerShell preference variables. Unlike the preference
29+
by using the PowerShell preference variables. Unlike the preference
3030
variables, the common parameters affect only the commands in which they are
3131
used.
3232

@@ -114,7 +114,7 @@ Valid values:
114114

115115
- Stop. Displays the error message and stops executing the command.
116116

117-
- Suspend. This value is only available in Windows PowerShell workflows. When
117+
- Suspend. This value is only available in PowerShell workflows. When
118118
a workflow runs into terminating error, this action preference automatically
119119
suspends the job to allow for further investigation. After investigation,
120120
the workflow can be resumed.
@@ -215,7 +215,7 @@ are sent through the pipeline. If you omit this parameter, objects are sent as
215215
they are generated.
216216

217217
This resource management parameter is designed for advanced users. When you
218-
use this parameter, Windows PowerShell does not call the next cmdlet in the
218+
use this parameter, PowerShell does not call the next cmdlet in the
219219
pipeline until the number of objects generated equals OutBuffer + 1.
220220
Thereafter, it sends all objects as they are generated.
221221

@@ -413,7 +413,7 @@ command:
413413
PS> Remove-Item Date.csv -WhatIf
414414
```
415415

416-
Instead of removing the item, Windows PowerShell lists the operations it would
416+
Instead of removing the item, PowerShell lists the operations it would
417417
perform and the items that would be affected. This command produces the
418418
following output:
419419

@@ -445,7 +445,7 @@ Valid values:
445445
risk of the cmdlet.
446446

447447
For example, the following command uses the Confirm parameter with a
448-
Remove-Item command. Before removing the item, Windows PowerShell lists the
448+
Remove-Item command. Before removing the item, PowerShell lists the
449449
operations it would perform and the items that would be affected, and asks for
450450
approval.
451451

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Lists the cmdlets that are designed for use with PowerShell providers.
1515
## LONG DESCRIPTION
1616

1717
PowerShell includes a set of cmdlets that are specifically designed to manage
18-
the items in the data stores that are exposed by Windows PowerShell providers.
18+
the items in the data stores that are exposed by PowerShell providers.
1919
You can use these cmdlets in the same ways to manage all the different types
2020
of data that the providers make available to you. For more information about
2121
providers, type "get-help about_providers".

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ data from script logic.
1717

1818
### Long Description
1919

20-
Scripts that are designed for Windows PowerShell can have one or more
20+
Scripts that are designed for PowerShell can have one or more
2121
Data sections that contain only data. You can include one or more Data
2222
sections in any script, function, or advanced function. The content of
2323
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
2828
text, such as error messages and Help strings. It also isolates the code
2929
logic, which facilitates security and validation tests.
3030

31-
In Windows PowerShell, the Data section is used to support script
31+
In PowerShell, the Data section is used to support script
3232
internationalization. You can use Data sections to make it easier to
3333
isolate, locate, and process strings that will be translated into many
3434
user interface (UI) languages.
@@ -49,7 +49,7 @@ The Data keyword is required. It is not case-sensitive.
4949

5050
The permitted content is limited to the following elements:
5151

52-
- All Windows PowerShell operators, except `-match`
52+
- All PowerShell operators, except `-match`
5353

5454
- `If`, `Else`, and `ElseIf` statements
5555

@@ -159,7 +159,7 @@ Simple data strings.
159159

160160
```powershell
161161
DATA {
162-
"Thank you for using my Windows PowerShell Organize.pst script."
162+
"Thank you for using my PowerShell Organize.pst script."
163163
"It is provided free of charge to the community."
164164
"I appreciate your comments and feedback."
165165
}

0 commit comments

Comments
 (0)