Use descriptive variable names in documentation examples

Replace generic names (modifier, modifier2, matcher, matcher2) with
descriptive names that reflect their purpose:
- markAsHot, setIndustry, activateAccounts, applyTemplate
- isTechAcme, isActive, isHighValueTech

Author: ipavlic

website/docs/api/function/MatchFields.md

@@ -19,13 +19,13 @@ IncompleteMatchFields field(String fieldPath)
 **Example**
 ```apex
 // Chain multiple field conditions
-MatchFields matcher = Fn.Match.field(Account.Name).equals('Acme')
+MatchFields isHighValueTech = Fn.Match.field(Account.Name).equals('Acme')
     .also(Account.AnnualRevenue).greaterThan(100000)
     .field(Account.Industry).equals('Technology');
 
 // Use in filtering
-SObjectCollection filtered = accounts.filter(matcher);
+SObjectCollection filtered = accounts.filter(isHighValueTech);
 
 // Use with call() from SObjectPredicate interface
-Boolean matches = matcher.call(myAccount);
+Boolean matches = isHighValueTech.call(myAccount);
 ```

website/docs/api/function/MatchRecordFields.md

@@ -16,16 +16,16 @@ public MatchRecordFields(SObject prototype)
 **Example**
 ```apex
 // Create matcher from prototype
-MatchRecordFields matcher = new MatchRecordFields(new Account{
+MatchRecordFields isTechAcme = new MatchRecordFields(new Account{
     Name = 'Acme Corp',
     Industry = 'Technology'
 });
 
 // Or use via Fn.Match
-MatchRecordFields matcher2 = Fn.Match.recordFields(new Account{Status__c = 'Active'});
+MatchRecordFields isActive = Fn.Match.recordFields(new Account{Status__c = 'Active'});
 
 // Test records
-matcher.call(new Account{Name = 'Acme Corp', Industry = 'Technology'}); // true
-matcher.call(new Account{Name = 'Acme Corp', Industry = 'Technology', AnnualRevenue = 1000000}); // true (extra fields ignored)
-matcher.call(new Account{Name = 'Other Corp', Industry = 'Technology'}); // false
+isTechAcme.call(new Account{Name = 'Acme Corp', Industry = 'Technology'}); // true
+isTechAcme.call(new Account{Name = 'Acme Corp', Industry = 'Technology', AnnualRevenue = 1000000}); // true (extra fields ignored)
+isTechAcme.call(new Account{Name = 'Other Corp', Industry = 'Technology'}); // false
 ```

website/docs/api/function/ModifySObject.md

@@ -17,15 +17,15 @@ ModifySObject setField(Schema.SObjectField field, Object value)
 **Example**
 ```apex
 // Using field token
-ModifySObject modifier = Fn.Modify
+ModifySObject markAsHot = Fn.Modify
     .setField(Account.Status__c, 'Active')
     .setField(Account.Rating, 'Hot');
 
 // Using string field name
-ModifySObject modifier2 = Fn.Modify.setField('Industry', 'Technology');
+ModifySObject setIndustry = Fn.Modify.setField('Industry', 'Technology');
 
 // Apply to collection
-accounts.forEach(modifier);
+accounts.forEach(markAsHot);
 ```
 
 ## setFields
@@ -45,9 +45,9 @@ Map<Schema.SObjectField, Object> updates = new Map<Schema.SObjectField, Object>{
     Account.Status__c => 'Active',
     Account.Rating => 'Hot'
 };
-ModifySObject modifier = Fn.Modify.setFields(updates);
+ModifySObject activateAccounts = Fn.Modify.setFields(updates);
 
 // Using prototype SObject
 Account prototype = new Account(Status__c = 'Active', Rating = 'Hot');
-ModifySObject modifier2 = Fn.Modify.setFields(prototype);
+ModifySObject applyTemplate = Fn.Modify.setFields(prototype);
 ```