From 95431c9dd13f5771375e9d74f78abb99fa78530d Mon Sep 17 00:00:00 2001
From: Christoph Bergmeister <c.bergmeister@gmail.com>
Date: Sat, 15 Mar 2025 16:52:48 +0000
Subject: [PATCH] Document new optional parameters added in 1704

---
 docs/Rules/UseCorrectCasing.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/docs/Rules/UseCorrectCasing.md b/docs/Rules/UseCorrectCasing.md
index 3d6c3d5a9..bbb7618e4 100644
--- a/docs/Rules/UseCorrectCasing.md
+++ b/docs/Rules/UseCorrectCasing.md
@@ -16,6 +16,35 @@ 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.
 
+## Configuration
+
+```powershell
+Rules = @{
+    PS UseCorrectCasing = @{
+        Enable        = $true
+        CheckCommands = $true
+        CheckKeyword  = $true
+        CheckOperator = $true
+    }
+}
+```
+
+### Enable: bool (Default value is `$false`)
+
+Enable or disable the rule during ScriptAnalyzer invocation.
+
+### CheckCommands: bool (Default value is `$true`)
+
+If true, require the case of all operators to be lowercase.
+
+### CheckKeyword: bool (Default value is `$true`)
+
+If true, require the case of all keywords to be lowercase.
+
+### CheckOperator: bool (Default value is `$true`)
+
+If true, require the case of all commands to match their actual casing.
+
 ## How
 
 Use exact casing for type names.