Merge branch 'sdw-w406969-pssa-124' into 24.0-docsbackport

Author: sdwheeler

docs/Rules/AvoidDefaultValueSwitchParameter.md

@@ -74,4 +74,4 @@ function Test-Script
 - [Strongly Encouraged Development Guidelines][01]
 
 <!-- link references -->
-[01]: /powershell/scripting/developer/cmdlet/strongly-encouraged-development-guidelines#parameters-that-take-true-and-false
+[01]: https://learn.microsoft.com/powershell/scripting/developer/cmdlet/strongly-encouraged-development-guidelines#parameters-that-take-true-and-false

docs/Rules/AvoidUsingConvertToSecureStringWithPlainText.md

@@ -1,6 +1,6 @@
 ---
 description: Avoid Using SecureString With Plain Text
-ms.date: 06/28/2023
+ms.date: 01/28/2025
 ms.topic: reference
 title: AvoidUsingConvertToSecureStringWithPlainText
 ---

docs/Rules/UseCorrectCasing.md

@@ -10,35 +10,26 @@ title: UseCorrectCasing
 
 ## Description
 
-This is a style/formatting rule. PowerShell is case insensitive wherever possible,
-so the casing of cmdlet names, parameters, keywords and operators does not matter.
-This rule nonetheless ensures consistent casing for clarity and readability.
-Using lowercase keywords helps distinguish them from commands.
-Using lowercase operators helps distinguish them from parameters.
+This is a style formatting rule. PowerShell is case insensitive where applicable. The casing of
+cmdlet names or parameters does not matter but this rule ensures that the casing matches for
+consistency and also because most cmdlets/parameters start with an upper case and using that
+improves readability to the human eye.
 
 ## How
 
-Use exact casing for type names.
-
 Use exact casing of the cmdlet and its parameters, e.g.
 `Invoke-Command { 'foo' } -RunAsAdministrator`.
 
-Use lowercase for language keywords and operators.
-
 ## Example
 
 ### Wrong
 
 ```powershell
-ForEach ($file IN get-childitem -recurse) {
-    $file.Extension -Eq '.txt'
-}
+invoke-command { 'foo' } -runasadministrator
 ```
 
 ### Correct
 
 ```powershell
-foreach ($file in Get-ChildItem -Recurse) {
-    $file.Extension -eq '.txt'
-}
+Invoke-Command { 'foo' } -RunAsAdministrator
 ```

docs/Rules/UseShouldProcessForStateChangingFunctions.md

@@ -74,5 +74,5 @@ function Set-ServiceObject
 <!-- link references -->
 [01]: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_functions_cmdletbindingattribute
 [02]: https://learn.microsoft.com/powershell/scripting/developer/cmdlet/requesting-confirmation-from-cmdlets
-[03]: https://learn.microsoft.com/powershell/scripting/developer/cmdlet/required-development-guidelines
+[03]: https://learn.microsoft.com/powershell/scripting/developer/cmdlet/required-development-guidelines#support-confirmation-requests-rd04
 [04]: https://learn.microsoft.com/powershell/scripting/learn/deep-dives/everything-about-shouldprocess

docs/Rules/UseUTF8EncodingForHelpFile.md

@@ -28,6 +28,6 @@ save files with a specific encoding.
 For more information, see the following articles:
 
 - [System.IO.StreamReader](xref:System.IO.StreamReader.CurrentEncoding%2A)
-- [about_Character_Encoding](/powershell/module/microsoft.powershell.core/about/about_character_encoding)
+- [about_Character_Encoding](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_character_encoding)
 - [Set-Content](xref:Microsoft.PowerShell.Management.Set-Content)
-- [Understanding file encoding in VS Code and PowerShell](/powershell/scripting/dev-cross-plat/vscode/understanding-file-encoding)
+- [Understanding file encoding in VS Code and PowerShell](https://learn.microsoft.com/powershell/scripting/dev-cross-plat/vscode/understanding-file-encoding)