7/18/2024 PM Publish

reference/5.1/CimCmdlets/Get-CimAssociatedInstance.md

@@ -3,7 +3,7 @@ external help file: Microsoft.Management.Infrastructure.CimCmdlets.dll-Help.xml
 Locale: en-US
 Module Name: CimCmdlets
 ms.date: 05/31/2024
-online version: https://learn.microsoft.com/powershell/module/cimcmdlets/get-cimassociatedinstance?view=powershell-7.4&WT.mc_id=ps-gethelp
+online version: https://learn.microsoft.com/powershell/module/cimcmdlets/get-cimassociatedinstance?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Get-CimAssociatedInstance
 ---

reference/5.1/Microsoft.PowerShell.Core/About/about_Intrinsic_Members.md

@@ -2,7 +2,7 @@
 description: Describes automatic members in all PowerShell objects
 Locale: en-US
 ms.date: 01/10/2024
-online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Inrinsic_Members?view=powershell-5.1&WT.mc_id=ps-gethelp
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Intrinsic_Members?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Intrinsic_Members
 ---

reference/5.1/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

@@ -66,9 +66,10 @@ preferences. For more information about these environment variables, see
 - `$env:PSModulePath`
 
 > [!NOTE]
-> Changes to preference variable only take effect in scripts and functions if
-> those scripts or functions are defined in the same scope as the scope in
-> which preference was used. For more information, see [about_Scopes][40].
+> Changes to preference variables apply only in the scope they are made
+> and any child scopes thereof. For example, you can limit the effects of
+> changing a preference variable to a single function or script. For more
+> information, see [about_Scopes][40].
 
 ## Working with preference variables
 
@@ -119,7 +120,8 @@ enumeration values: **High**, **Medium**, **Low**, or **None**.
 Cmdlets and functions are assigned a risk of **High**, **Medium**, or **Low**.
 When the value of the `$ConfirmPreference` variable is less than or equal to
 the risk assigned to a cmdlet or function, PowerShell automatically prompts you
-for confirmation before running the cmdlet or function.
+for confirmation before running the cmdlet or function. For more information
+about assigning a risk to cmdlets or functions, see [about_Functions_CmdletBindingAttribute][65].
 
 If the value of the `$ConfirmPreference` variable is **None**, PowerShell never
 automatically prompts you before running a cmdlet or function.
@@ -167,11 +169,11 @@ Cmdlets and functions that might pose a risk to the system have a **Confirm**
 parameter that you can use to request or suppress confirmation for a single
 command.
 
-Because most cmdlets and functions use the default risk value,
-**ConfirmImpact**, of **Medium**, and the default value of `$ConfirmPreference`
-is **High**, automatic confirmation rarely occurs. However, you can activate
-automatic confirmation by changing the value of `$ConfirmPreference` to
-**Medium** or **Low**.
+Most cmdlets and functions keep the default value of **Medium** for **ConfirmImpact**.
+`$ConfirmPreference` is set to **High** by default. Therefore, it's rare that commands
+automatically prompt for confirmation when users don't specify the **Confirm** parameter.
+To extend automatic confirmation prompting to more cmdlets and functions, set the value
+of `$ConfirmPreference` to **Medium** or **Low**.
 
 ### Examples
 
@@ -1770,3 +1772,4 @@ At line:1 char:1
 [62]: xref:System.Text.UTF32Encoding
 [63]: xref:System.Text.UTF7Encoding
 [64]: xref:System.Text.UTF8Encoding
+[65]: about_Functions_CmdletBindingAttribute.md

reference/7.2/Microsoft.PowerShell.Core/About/about_Intrinsic_Members.md

@@ -2,7 +2,7 @@
 description: Describes automatic members in all PowerShell objects
 Locale: en-US
 ms.date: 01/10/2024
-online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Inrinsic_Members?view=powershell-7.2&WT.mc_id=ps-gethelp
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Intrinsic_Members?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Intrinsic_Members
 ---

reference/7.2/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

@@ -63,9 +63,10 @@ preferences. For more information about these environment variables, see
 - `$env:PSModulePath`
 
 > [!NOTE]
-> Changes to preference variable only take effect in scripts and functions if
-> those scripts or functions are defined in the same scope as the scope in
-> which preference was used. For more information, see [about_Scopes][38].
+> Changes to preference variables apply only in the scope they are made
+> and any child scopes thereof. For example, you can limit the effects of
+> changing a preference variable to a single function or script. For more
+> information, see [about_Scopes][38].
 
 ## Working with preference variables
 
@@ -116,7 +117,8 @@ enumeration values: **High**, **Medium**, **Low**, or **None**.
 Cmdlets and functions are assigned a risk of **High**, **Medium**, or **Low**.
 When the value of the `$ConfirmPreference` variable is less than or equal to
 the risk assigned to a cmdlet or function, PowerShell automatically prompts you
-for confirmation before running the cmdlet or function.
+for confirmation before running the cmdlet or function. For more information
+about assigning a risk to cmdlets or functions, see [about_Functions_CmdletBindingAttribute][64].
 
 If the value of the `$ConfirmPreference` variable is **None**, PowerShell never
 automatically prompts you before running a cmdlet or function.
@@ -164,11 +166,11 @@ Cmdlets and functions that might pose a risk to the system have a **Confirm**
 parameter that you can use to request or suppress confirmation for a single
 command.
 
-Because most cmdlets and functions use the default risk value,
-**ConfirmImpact**, of **Medium**, and the default value of `$ConfirmPreference`
-is **High**, automatic confirmation rarely occurs. However, you can activate
-automatic confirmation by changing the value of `$ConfirmPreference` to
-**Medium** or **Low**.
+Most cmdlets and functions keep the default value of **Medium** for **ConfirmImpact**.
+`$ConfirmPreference` is set to **High** by default. Therefore, it's rare that commands
+automatically prompt for confirmation when users don't specify the **Confirm** parameter.
+To extend automatic confirmation prompting to more cmdlets and functions, set the value
+of `$ConfirmPreference` to **Medium** or **Low**.
 
 ### Examples
 
@@ -1729,3 +1731,4 @@ At line:1 char:1
 [61]: xref:System.Text.UTF32Encoding
 [62]: xref:System.Text.UTF7Encoding
 [63]: xref:System.Text.UTF8Encoding
+[64]: about_Functions_CmdletBindingAttribute.md

reference/7.4/Microsoft.PowerShell.Core/About/about_Intrinsic_Members.md

@@ -2,7 +2,7 @@
 description: Describes automatic members in all PowerShell objects
 Locale: en-US
 ms.date: 01/10/2024
-online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Inrinsic_Members?view=powershell-7.4&WT.mc_id=ps-gethelp
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Intrinsic_Members?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Intrinsic_Members
 ---

reference/7.4/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

@@ -64,9 +64,10 @@ preferences. For more information about these environment variables, see
 - `$env:PSModulePath`
 
 > [!NOTE]
-> Changes to preference variable only take effect in scripts and functions if
-> those scripts or functions are defined in the same scope as the scope in
-> which preference was used. For more information, see [about_Scopes][40].
+> Changes to preference variables apply only in the scope they are made
+> and any child scopes thereof. For example, you can limit the effects of
+> changing a preference variable to a single function or script. For more
+> information, see [about_Scopes][40].
 
 ## Working with preference variables
 
@@ -117,7 +118,8 @@ enumeration values: **High**, **Medium**, **Low**, or **None**.
 Cmdlets and functions are assigned a risk of **High**, **Medium**, or **Low**.
 When the value of the `$ConfirmPreference` variable is less than or equal to
 the risk assigned to a cmdlet or function, PowerShell automatically prompts you
-for confirmation before running the cmdlet or function.
+for confirmation before running the cmdlet or function. For more information
+about assigning a risk to cmdlets or functions, see [about_Functions_CmdletBindingAttribute][66].
 
 If the value of the `$ConfirmPreference` variable is **None**, PowerShell never
 automatically prompts you before running a cmdlet or function.
@@ -165,11 +167,11 @@ Cmdlets and functions that might pose a risk to the system have a **Confirm**
 parameter that you can use to request or suppress confirmation for a single
 command.
 
-Because most cmdlets and functions use the default risk value,
-**ConfirmImpact**, of **Medium**, and the default value of `$ConfirmPreference`
-is **High**, automatic confirmation rarely occurs. However, you can activate
-automatic confirmation by changing the value of `$ConfirmPreference` to
-**Medium** or **Low**.
+Most cmdlets and functions keep the default value of **Medium** for **ConfirmImpact**.
+`$ConfirmPreference` is set to **High** by default. Therefore, it's rare that commands
+automatically prompt for confirmation when users don't specify the **Confirm** parameter.
+To extend automatic confirmation prompting to more cmdlets and functions, set the value
+of `$ConfirmPreference` to **Medium** or **Low**.
 
 ### Examples
 
@@ -1758,3 +1760,4 @@ At line:1 char:1
 [63]: xref:System.Text.UTF32Encoding
 [64]: xref:System.Text.UTF7Encoding
 [65]: xref:System.Text.UTF8Encoding
+[66]: about_Functions_CmdletBindingAttribute.md

reference/7.5/Microsoft.PowerShell.Core/About/about_Intrinsic_Members.md

@@ -2,7 +2,7 @@
 description: Describes automatic members in all PowerShell objects
 Locale: en-US
 ms.date: 01/10/2024
-online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Inrinsic_Members?view=powershell-7.5&WT.mc_id=ps-gethelp
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_Intrinsic_Members?view=powershell-7.5&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Intrinsic_Members
 ---

reference/7.5/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

@@ -64,9 +64,10 @@ preferences. For more information about these environment variables, see
 - `$env:PSModulePath`
 
 > [!NOTE]
-> Changes to preference variable only take effect in scripts and functions if
-> those scripts or functions are defined in the same scope as the scope in
-> which preference was used. For more information, see [about_Scopes][40].
+> Changes to preference variables apply only in the scope they are made
+> and any child scopes thereof. For example, you can limit the effects of
+> changing a preference variable to a single function or script. For more
+> information, see [about_Scopes][40].
 
 ## Working with preference variables
 
@@ -117,7 +118,8 @@ enumeration values: **High**, **Medium**, **Low**, or **None**.
 Cmdlets and functions are assigned a risk of **High**, **Medium**, or **Low**.
 When the value of the `$ConfirmPreference` variable is less than or equal to
 the risk assigned to a cmdlet or function, PowerShell automatically prompts you
-for confirmation before running the cmdlet or function.
+for confirmation before running the cmdlet or function. For more information
+about assigning a risk to cmdlets or functions, see [about_Functions_CmdletBindingAttribute][66].
 
 If the value of the `$ConfirmPreference` variable is **None**, PowerShell never
 automatically prompts you before running a cmdlet or function.
@@ -165,11 +167,11 @@ Cmdlets and functions that might pose a risk to the system have a **Confirm**
 parameter that you can use to request or suppress confirmation for a single
 command.
 
-Because most cmdlets and functions use the default risk value,
-**ConfirmImpact**, of **Medium**, and the default value of `$ConfirmPreference`
-is **High**, automatic confirmation rarely occurs. However, you can activate
-automatic confirmation by changing the value of `$ConfirmPreference` to
-**Medium** or **Low**.
+Most cmdlets and functions keep the default value of **Medium** for **ConfirmImpact**.
+`$ConfirmPreference` is set to **High** by default. Therefore, it's rare that commands
+automatically prompt for confirmation when users don't specify the **Confirm** parameter.
+To extend automatic confirmation prompting to more cmdlets and functions, set the value
+of `$ConfirmPreference` to **Medium** or **Low**.
 
 ### Examples
 
@@ -1758,3 +1760,4 @@ At line:1 char:1
 [63]: xref:System.Text.UTF32Encoding
 [64]: xref:System.Text.UTF7Encoding
 [65]: xref:System.Text.UTF8Encoding
+[66]: about_Functions_CmdletBindingAttribute.md

reference/docs-conceptual/community/contributing/get-started-writing.md

@@ -95,7 +95,7 @@ more information and best practices.
 [2]: https://github.com/MicrosoftDocs/PowerShell-Docs/tree/main/reference
 [3]: https://github.com/MicrosoftDocs/PowerShell-Docs/tree/main/reference/docs-conceptual
 [4]: https://github.com/PowerShell/powershell-rfc/blob/master/RFC0000-RFC-Process.md
-[5]: /contribute/#quick-edits-to-existing-documents
+[5]: /contribute/content/how-to-write-quick-edits
 [6]: /contribute/how-to-write-workflows-major#making-your-changes
 [7]: /contribute/get-started-setup-local#fork-the-repository
 [8]: pull-requests.md

reference/docs-conceptual/community/contributing/overview.md

@@ -96,7 +96,7 @@ Additional resources
 [7]: https://www.powershellgallery.com/packages/posh-git
 [8]: /contribute/get-started-setup-local
 [9]: /contribute/git-github-fundamentals
-[10]: /contribute/#quick-edits-to-existing-documents
+[10]: /contribute/content/how-to-write-quick-edits
 [11]: /contribute/how-to-write-workflows-major
 [12]: /contribute/style-quick-start
 [13]: /style-guide/welcome/

reference/docs-conceptual/toc.yml

@@ -353,6 +353,8 @@ items:
         href: community/hall-of-fame.md
       - name: What's new in Docs
         items:
+          - name: 2024 Updates
+            href: community/2024-updates.md
           - name: 2023 Updates
             href: community/2023-updates.md
           - name: 2022 Updates

reference/docs-conceptual/whats-new/unix-support.md

@@ -225,10 +225,10 @@ The following cmdlets aren't available on Linux and macOS:
 
 The following cmdlets are available with limitations:
 
-`Get-Clipboard` - available on Linux but not supported on macOS
-`Set-Clipboard` - available in PowerShell 7.0+
-`Restart-Computer` - available for Linux and macOS in PowerShell 7.1+
-`Stop-Computer` - available for Linux and macOS in PowerShell 7.1+
+- `Get-Clipboard` - available in PowerShell 7.0+
+- `Set-Clipboard` - available in PowerShell 7.0+
+- `Restart-Computer` - available for Linux and macOS in PowerShell 7.1+
+- `Stop-Computer` - available for Linux and macOS in PowerShell 7.1+
 
 ### Microsoft.PowerShell.Utility cmdlets