Add documentation for UseSupportsShouldProcess rule

Author: Kapil Borle

RuleDocumentation/README.md

@@ -44,6 +44,7 @@
 |[UsePSCredentialType](./UsePSCredentialType.md) | Warning|
 |[UseShouldProcessCorrectly](./UseShouldProcessCorrectly.md) | Warning|
 |[UseShouldProcessForStateChangingFunctions](./UseShouldProcessForStateChangingFunctions.md) | Warning|
+|[UseSupportsShouldProcess](./UseSupportsShouldProcess.md) | Warning|
 |[UseSingularNouns](./UseSingularNouns.md) | Warning|
 |[UseStandardDSCFunctionsInResource](./UseStandardDSCFunctionsInResource.md) | Error |
 |[UseToExportFieldsInManifest](./UseToExportFieldsInManifest.md) | Warning|

RuleDocumentation/UseSupportsShouldProcess.md

@@ -2,16 +2,26 @@
 **Severity Level: Warning**
 
 ## Description
-
-## How to Fix
+This rule discourages manual declaration of `whatif` and `confirm` parameters in a function/cmdlet. These parameters are, however, provided automatically when a function declares a `CmdletBinding` attribute with `SupportsShouldProcess` as its named argument. Using `SupportsShouldProcess` no only provides these parameters but also some generic functionality that allows the function/cmdlet authors to provide the desired interactive experience while using the cmdlet.
 
 ## Example
-### Wrong：
+### Wrong:
 ```PowerShell
-
+function foo {
+    param(
+        $param1,
+        $confirm,
+        $whatif
+    )
+}
 ```
 
 ### Correct:
 ```PowerShell
-
+function foo {
+    [CmdletBinding(SupportsShouldProcess)]
+    param(
+        $param1
+    )
+}
 ```