How resources support the guides
Resource pages exist so readers can move from an explanation to the evidence behind it. A plan guide should not force you to guess which xAI page, X Help page, app listing, or developer document was used. When a guide discusses pricing, availability, privacy settings, model behavior, or API access, the resource pages show the kinds of sources that should be checked before acting.
When to use these pages
Use official links when you want the current vendor page, image credits when you want to understand where a visual came from, and the glossary when a term needs a plain-English definition. The pages are intentionally separate because each solves a different reader task: verification, visual context, and terminology.
How to read changing information
Grok, xAI, X, and competing AI products can change plan names, app features, data controls, and model labels quickly. Treat resources as a starting point for verification, then read the linked guide for interpretation. If a source changes and a page no longer reflects it, the corrections page explains how to report the issue.