The FAQ content is accurate and well-structured, so I made minimal changes to improve conversational tone and clarity. I replaced formal phrases with more direct, conversational language: changed 'Do not use' to 'Don't use' and 'are not best practices' to 'aren't best practices' to align with the brand guidelines for conversational writing. I also changed 'Do not include' to 'Don't include' for consistency. These changes maintain all existing technical content while making the tone more approachable and easier to scan.
For security rules selected:
- **ApexCRUDViolation**: This rule directly relates to point #6 in the FAQ about enforcing CRUD and FLS checks in Apex code. The FAQ specifically mentions 'Enforce CRUD (Create, Read, Update, Delete) and FLS (Field-Level Security) checks in Apex code to prevent unauthorized access,' which is exactly what this rule validates.
- **ApexSharingViolations**: This rule relates to multiple points in the FAQ about sharing and access control, particularly points #1 (Guest User Sharing Rules), #3 (Avoid Manual Sharing), #5 (System Mode for Critical Operations), and #8 (Avoid Public Groups for Guest Users). The FAQ discusses various sharing mechanisms and access patterns that this rule would evaluate for security compliance.