diff --git a/RuleDocumentation/PossibleIncorrectComparisonWithNull.md b/RuleDocumentation/PossibleIncorrectComparisonWithNull.md
index d0e186521..bfcde4672 100644
--- a/RuleDocumentation/PossibleIncorrectComparisonWithNull.md
+++ b/RuleDocumentation/PossibleIncorrectComparisonWithNull.md
@@ -41,6 +41,18 @@ function Test-CompareWithNull
 ## Try it Yourself
 
 ``` PowerShell
-if (@() -eq $null) { 'true' } else { 'false' }  # Returns false
-if ($null -ne @()) { 'true' } else { 'false' }  # Returns true
+# Both expressions below return 'false' because the comparison does not return an object and therefore the if statement always falls through:
+if (@() -eq $null) { 'true' } else { 'false' }
+if (@() -ne $null) { 'true' }else { 'false' } 
+```
+This is just the way how the comparison operator works (by design) but as demonstrated this can lead to unintuitive behaviour, especially when the intent is just a null check. The following example demonstrated the designed behaviour of the comparison operator, whereby for each element in the collection, the comparison with the right hand side is done, and where true, that element in the collection is returned.
+``` PowerShell
+PS> 1,2,3,1,2 -eq $null
+PS> 1,2,3,1,2 -eq 1    
+1
+1
+PS> (1,2,3,1,2 -eq $null).count            
+0
+PS> (1,2,$null,3,$null,1,2 -eq $null).count
+2
 ```