Fix heading capitalization in enterprise-contracting

enterprise-contracting.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Enterprise contracting"
 description: "How Mintlify approaches enterprise legal review, MSA negotiations, security questionnaires, and procurement so you know what to expect when buying."
 hidden: true
 ---
 
@@ -45,7 +45,7 @@
 These are structural to how the platform operates. We'll explain each one—not to justify ourselves, but because understanding the reason usually resolves the concern.
 
 <AccordionGroup>
-  <Accordion title="1. Platform IP Ownership">
+  <Accordion title="1. Platform IP ownership">
     **Our position:** Mintlify owns all platform code, features, and methods.
     Customers own all of their content and data.
 
@@ -54,39 +54,39 @@
     **What this means for you:** Your content, your data, and your documentation output are entirely yours. We make no claim on any of it.
   </Accordion>
 
-  <Accordion title="2. Aggregate Data for Product Analytics">
+  <Accordion title="2. Aggregate data for product analytics">
     **Our position:** Mintlify may use de-identified, aggregated usage data (feature usage, performance metrics, search patterns) for product analytics and improvement.
 
     **Why:** Understanding how features perform across the platform is how we know what to build and how to optimize. Without usage patterns, we're flying blind—and so are you when you rely on us to keep improving.
 
     **What this means for you:** We analyze aggregate signals, not your content. Your specific documentation, your users' data, and any identifiable information are never surfaced or shared.
   </Accordion>
 
-  <Accordion title="3. Capped Liability">
+  <Accordion title="3. Capped liability">
     **Our position:** Standard cap is 12 months of fees. For large deals, we go higher. We do not accept unlimited liability.
 
     **Why:** Uncapped exposure makes us uninsurable, which means we'd have to price for worst-case scenarios or decline customer relationships entirely. Neither outcome serves you.
 
     **What this means for you:** We accept a 2x annual fees super-cap for the categories that matter most: confidentiality breaches, data security incidents, and IP indemnification. We feel this is fair for elevated risk categories, and it's backed by insurance.
   </Accordion>
 
-  <Accordion title="4. No Sublicensing">
+  <Accordion title="4. No sublicensing">
     **Our position:** Customers may not resell or redistribute platform access.
 
     **Why:** Our security model, pricing, and support commitments are built around direct relationships with known customers. Sublicensing creates distribution we can't monitor, secure, or support.
 
     **What this means for you:** Affiliate use within your corporate family—subsidiaries, related entities, M&A scenarios—is fully accommodated under standard enterprise terms.
   </Accordion>
 
-  <Accordion title="5. Warranty Limitations">
+  <Accordion title="5. Warranty limitations">
     **Our position:** We warrant platform uptime per our SLA. We provide everything else on standard "as-is" SaaS terms.
 
     **Why:** We use third-party LLM providers whose output we can't warrant. No software company can guarantee outcomes that depend on customer data, use cases, or third-party integrations.
 
     **What this means for you:** We will warrant in writing that our LLM providers are contractually prohibited from using your data for model training or improvement—which is the protection that actually matters.
   </Accordion>
 
-  <Accordion title="6. No Termination for Convenience">
+  <Accordion title="6. No termination for convenience">
     **Our position:** Either party may end the agreement for material breach with a 30-day cure period.
 
     **Why:** A unilateral walk right eliminates the economic basis for our pricing.