reorganize page for clarity

Author: devalog

.vale/styles/FernStyles/Acronyms.yml

@@ -68,3 +68,4 @@ exceptions:
   - MDX # Fern-specific
   - SEO # Fern-specific
   - AWS # Fern-specific
+  - LLM # Fern-specific

fern/products/docs/pages/seo/llms-txt.mdx

@@ -1,40 +1,23 @@
 ---
 title: llms.txt
-subtitle: Enable tools like Cursor, GitHub Copilot, ChatGPT, and Claude to quickly understand your documentation.
-description: Learn how your documentation becomes accessible to AI tools using the llms.txt standard. Make your docs AI-friendly.
-layout: guide
+description: Enable tools like Cursor, GitHub Copilot, ChatGPT, and Claude to understand your documentation.
 ---
 
-## What is llms.txt?
-[LLMs.txt](https://llmstxt.org/) is an emerging standard so that websites can easily expose information to AI developer tools.
-LLMs thrive on concise, structured information, and `llms.txt` help them locate and interpret key information in your developer documentation with ease.
-No configuration required--your `llms.txt` files are automatically generated and maintained, just like a `sitemap.xml` or `robots.txt`.
+[llms.txt](https://llmstxt.org/) is a standard for exposing website content to AI developer tools. Fern automatically generates and maintains `llms.txt` and `llms-full.txt` files for your documentation site.
 
-### llms.txt
-- **Small and fast**: Quick to load and easy to parse.
-- **Summary-focused**: Each page distilled into a one-sentence description with its URL.
-- **Structured for AI**: Helps tools understand the overall structure of your documentation.
+## `llms.txt`
 
-See an example: [docs.cohere.com/llms.txt](https://docs.cohere.com/llms.txt)
-
-### llms-full.txt
-- **Comprehensive**: Includes the full content of your documentation.
-- **API-ready**: Automatically incorporates your complete API Reference with resolved OpenAPI specifications and SDK code examples for all languages you've enabled. Each API endpoint page includes its full OpenAPI spec.
-- **Token efficient**: When Fern detects an LLM bot, it automatically serves Markdown content from the llms.txt file  instead of HTML, reducing token consumption by 90%+.
-
-See an example: [docs.cohere.com/llms-full.txt](https://docs.cohere.com/llms-full.txt)
+Contains a lightweight summary of your documentation site with each page distilled into a one-sentence description and URL. The format is structured to help AI tools parse and understand your documentation's hierarchy and organization.
 
-## Analytics and monitoring
+See an example: [docs.cohere.com/llms.txt](https://docs.cohere.com/llms.txt)
 
-Fern tracks comprehensive analytics for llms.txt usage in the Fern Dashboard, including:
-- LLM traffic by provider (Claude, ChatGPT, Cursor, etc.)
-- Traffic breakdown for .md and llms.txt files by agents and humans
+## `llms-full.txt`
 
-This visibility helps you understand LLM traffic patterns and optimize your documentation for AI consumption.
+Contains complete documentation content including the full text of all pages. For API documentation, this includes your complete API Reference with resolved OpenAPI specifications and SDK code examples for enabled languages. Each API endpoint page includes its full OpenAPI spec.
 
-## View in action
+When Fern detects an LLM bot accessing your documentation, it automatically serves Markdown instead of HTML, reducing token consumption by 90%+.
 
-Check out the llms.txt files for this site:
+View the llms.txt files for this site:
 - `https://buildwithfern.com/learn/llms.txt`
 - `https://buildwithfern.com/learn/llms-full.txt`
 
@@ -45,3 +28,12 @@ Check out the llms.txt files for this site:
     className="rounded-lg border border-gray-200 dark:border-gray-700"
   />
 </Frame>
+
+## Analytics and monitoring
+
+The [Fern Dashboard](https://dashboard.buildwithfern.com/) provides comprehensive analytics for llms.txt usage including:
+- Traffic by LLM provider (Claude, ChatGPT, Cursor, etc.)
+- Page-level breakdowns of bot vs. human visitors for `.md` and `llms.txt` files
+
+This visibility helps you understand LLM traffic patterns and optimize your documentation for AI consumption.
+