Replaced duplicate link and improved examples for $null (#273)

* Replaced duplicate link

* Fixes AB#304282

Author: sdwheeler

reference/docs-conceptual/PSScriptAnalyzer/Rules/PossibleIncorrectComparisonWithNull.md

@@ -1,6 +1,6 @@
 ---
 description: Null Comparison
-ms.date: 06/28/2023
+ms.date: 12/03/2024
 ms.topic: reference
 title: PossibleIncorrectComparisonWithNull
 ---
@@ -18,8 +18,8 @@ There are multiple reasons why this occurs:
 - `$null` is a scalar value. When the value on the left side of an operator is a scalar, comparison
   operators return a **Boolean** value. When the value is a collection, the comparison operators
   return any matching values or an empty array if there are no matches in the collection.
-- PowerShell performs type casting left to right, resulting in incorrect comparisons when `$null` is
-  cast to other scalar types.
+- PowerShell performs type casting on the right-hand operand, resulting in incorrect comparisons
+  when `$null` is cast to other scalar types.
 
 The only way to reliably check if a value is `$null` is to place `$null` on the left side of the
 operator so that a scalar comparison is performed.
@@ -55,10 +55,10 @@ function Test-CompareWithNull
 ## Try it Yourself
 
 ```powershell
-# Both expressions below return 'false' because the comparison does not return an
-# object and therefore the if statement always falls through:
+# This example returns 'false' because the comparison does not return any objects from the array
 if (@() -eq $null) { 'true' } else { 'false' }
-if (@() -ne $null) { 'true' } else { 'false' }
+# This example returns 'true' because the array is empty
+if ($null -ne @()) { 'true' } else { 'false' }
 ```
 
 This is how the comparison operator works by-design. But, as demonstrated, this can lead

reference/docs-conceptual/PSScriptAnalyzer/rules-recommendations.md

@@ -1,6 +1,6 @@
 ---
 description: This article lists best-practice recommendations and the rules associated with them.
-ms.date: 06/28/2023
+ms.date: 12/03/2024
 title: PSScriptAnalyzer rules and recommendations
 ---
 # PSScriptAnalyzer rules and recommendations
@@ -23,7 +23,7 @@ No rules defined.
 - Cmdlets names with unusable characters [AvoidReservedCharInCmdlet][30]
 - Parameter names that can't be used [AvoidReservedParams][31]
 - Support confirmation requests [UseShouldProcessForStateChangingFunctions][37] and
-  [UseShouldProcessForStateChangingFunctions][37]
+  [UseSupportsShouldProcess][39]
 - Must call **ShouldProcess** when the **ShouldProcess** attribute is present and vice versa
   [UseShouldProcess][32]
 - Nouns should be singular [UseSingularNouns][38]
@@ -222,6 +222,7 @@ No rules defined.
 [36]: Rules/UsePSCredentialType.md
 [37]: Rules/UseShouldProcessForStateChangingFunctions.md
 [38]: Rules/UseSingularNouns.md
+[39]: Rules/UseSupportsShouldProcess.md
 [116]: https://github.com/PowerShell/PSScriptAnalyzer/issues/116
 [130]: https://github.com/PowerShell/PSScriptAnalyzer/issues/130
 [131]: https://github.com/PowerShell/PSScriptAnalyzer/issues/131