Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #11118 - Fix typos in 5.1 topics #11119

Merged
merged 1 commit into from
May 16, 2024
Merged

Fixes #11118 - Fix typos in 5.1 topics #11119

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes the PowerShell execution policies and explains how to manage them.
Locale: en-US
ms.date: 03/04/2024
ms.date: 05/16/2024
no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings]
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1&WT.mc_id=ps-gethelp
schema: 2.0.0
Expand Down Expand Up @@ -268,7 +268,7 @@ policy.
For example:

```powershell
pwsh.exe -ExecutionPolicy AllSigned
powershell.exe -ExecutionPolicy AllSigned
```

The execution policy that you set isn't stored in the registry. Instead, it's
Expand Down Expand Up @@ -329,7 +329,7 @@ evaluates the execution policies in the following precedence order:
```
Group Policy: MachinePolicy
Group Policy: UserPolicy
Execution Policy: Process (or pwsh.exe -ExecutionPolicy)
Execution Policy: Process (or powershell.exe -ExecutionPolicy)
Execution Policy: LocalMachine
Execution Policy: CurrentUser
```
Expand Down
8 changes: 4 additions & 4 deletions reference/5.1/Microsoft.PowerShell.Core/About/about_Functions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes how to create and use functions in PowerShell.
Locale: en-US
ms.date: 03/12/2024
ms.date: 05/16/2024
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_functions?view=powershell-5.1&WT.mc_id=ps-gethelp
schema: 2.0.0
title: about Functions
Expand Down Expand Up @@ -38,8 +38,8 @@ output returned from your function. However, the `return` keyword exits the
function at that line. For more information, see [about_Return][16].

The function's statement list can contain different types of statement lists
with the keywords `begin`, `process`, `end`, and `clean`. These statement lists
handle input from the pipeline differently.
with the keywords `begin`, `process`, and `end`. These statement lists handle
input from the pipeline differently.

The [filter][04] keyword is used to create a type of function that runs on each
object in the pipeline. A filter resembles a function with all its statements
Expand Down Expand Up @@ -138,7 +138,7 @@ For more information, see [about_Automatic_Variables][15].
that reaches the function.
- If the pipeline input that reaches the function is empty, the `process` block
**does not** execute.
- The `begin`, `end`, and `clean` blocks still execute.
- The `begin` and `end` blocks still execute.

> [!IMPORTANT]
> If a function parameter is set to accept pipeline input, and a `process`
Expand Down