docs(FC0002): describe generic type argument and object reference casing (#162)

Describe generic type argument, object reference casing and namespace-qualified object reference

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Arthurvdv

content/docs/analyzers/FormattingCop/FC0002.md

@@ -41,6 +41,65 @@ codeunit 50100 MyCodeunit
 }
 ```
 
+### Generic type arguments
+
+FC0002 checks the casing of types used as generic type arguments inside `List of [...]`, `Dictionary of [...]`, and other generic type declarations. Both built-in type keywords and subtype keywords are checked:
+
+```al
+codeunit 50100 MyCodeunit
+{
+    var
+        Names: List of [TEXT]; // Casing mismatch: TEXT should be Text [FC0002]
+        Lookup: Dictionary of [INTEGER, TEXT]; // Two casing mismatches [FC0002]
+        Nested: List of [Dictionary of [Integer, TEXT]]; // [FC0002]
+}
+```
+
+### Object reference casing
+
+FC0002 checks the casing of object names referenced in `Record`, `Codeunit`, `Interface`, `Page`, `XmlPort`, and other subtyped data type declarations. The object name must match the casing of the original declaration:
+
+```al
+codeunit 50100 MyCodeunit
+{
+    var
+        Cust: Record "MY CUSTOMER"; // Casing mismatch [FC0002]
+        Svc: Codeunit "MYHELPER"; // Casing mismatch [FC0002]
+}
+
+table 50100 "My Customer"
+{
+    fields
+    {
+        field(1; "Primary Key"; Integer) { }
+    }
+}
+
+codeunit 50101 MyHelper { }
+```
+
+This applies to global variables, local variables, parameters, and return values. Namespace-qualified references are also checked, including the casing of each namespace part:
+
+```al
+namespace MyPublisher.MyExtension.MyAppDomain;
+
+codeunit 50100 MyCodeunit
+{
+    var
+        Cust: Record MYPUBLISHER.MYEXTENSION.MYAPPDOMAIN.MYTABLE; // Four casing mismatches [FC0002]
+}
+
+table 50100 MyTable
+{
+    fields
+    {
+        field(1; "Primary Key"; Integer) { }
+    }
+}
+```
+
+Object references by numeric ID (`Record 50100`) are not checked.
+
 ### XmlPort vs Xmlport casing
 
 The AL language intentionally uses different canonical casings for xmlports depending on the context. FC0002 follows the compiler's own canonical names (the same names the AL Language extension's IntelliSense suggests) rather than enforcing a single spelling: