Skip to content

Commit 2536757

Browse files
committed
more typos
1 parent 6e803bb commit 2536757

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

reference/docs-conceptual/install/install-powershell-on-windows.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ different scenarios and workflows. Choose the method that best suits your needs.
2323
- [MSI package][09] - Best choice for Windows Servers and enterprise deployment scenarios
2424
- [MSIX package][10] - An easy way to install for casual users of PowerShell but has limitations
2525
- [ZIP package][12] - Easiest way to _side load_ or install multiple versions or install on Windows
26-
Core Server, Windows IoT, and Arm-based systems
26+
Server Core, Windows IoT, and Arm-based systems
2727
- [.NET Global tool][08] - A good choice for .NET developers that install and use other global tools
2828

2929
### Install PowerShell using WinGet
@@ -71,9 +71,9 @@ winget install --id Microsoft.PowerShell --source winget --installer-type wix
7171
Alternatively, you can manually download and install the [MSI package][09].
7272

7373
Beginning with the winget package for PowerShell 7.7.0-preview.1, there is no MSI package available.
74-
Winget only installs the MSIX package.
74+
WinGet only installs the MSIX package.
7575

76-
Using the following command to install PowerShell 7.7-preview packages:
76+
Use the following command to install PowerShell 7.7-preview packages:
7777

7878
```powershell
7979
winget install --id Microsoft.PowerShell.Preview --source winget
@@ -278,8 +278,8 @@ If you aren't sure how PowerShell was installed, you can check the value of the
278278
which always points to the directory containing PowerShell that the current session is running.
279279

280280
- If the value is `$HOME\.dotnet\tools`, PowerShell was installed with the [.NET Global tool][08].
281-
- If the value is `$Env:ProgramFiles\PowerShell\7`, PowerShell was probably installed using the [MSI
282-
package][09]. You can verify this by looking for PowerShell in the **Programs and Features**
281+
- If the value is `$Env:ProgramFiles\PowerShell\7`, PowerShell was probably installed using the
282+
[MSI package][09]. You can verify this by looking for PowerShell in the **Programs and Features**
283283
Control Panel.
284284
- If the value starts with `$Env:ProgramFiles\WindowsApps\`, PowerShell was installed using the
285285
[MSIX package][10].
@@ -298,7 +298,7 @@ following command to upgrade PowerShell using WinGet:
298298
winget upgrade --id Microsoft.PowerShell
299299
```
300300

301-
If available in the new version, Winget uses the same package format (MSI or MSIX) that was used to
301+
If available in the new version, WinGet uses the same package format (MSI or MSIX) that was used to
302302
install the current version of PowerShell. Alternatively, you can manually download and install
303303
the package you want.
304304

0 commit comments

Comments
 (0)