docs(features):added accuracy in by listing regions instead of global usage support.

[offsideDebugger]

📋 Description

Added a new Regional Availability Section in the features/appstore-digital-goods, because as per issue #98 apple does not allow world wide IAP support on Appstore storefronts, so made a separate section just below Introduction which will help developers to get an idea whether they can integrate Dodo payments as IAP replacement in their respective region.

🎯 Type of Change

• 📝 Documentation update (improving existing docs)
• ✨ New documentation (adding new guides, API docs, etc.)
• 🐛 Bug fix (fixing errors, broken links, incorrect information)
• 🎨 Style/formatting (improving readability, fixing formatting)
• 🏗️ Structural change (reorganizing content, navigation updates)
• 🌐 Translation (adding or improving translations)
• 🖼️ Assets (adding or updating images, diagrams)

📖 What documentation does this PR affect?

• Getting Started / Setup
• API Reference
• Developer Resources
• Integration Guides
• Features Documentation
• External Integrations
• Changelog
• Other:

✅ Checklist

• I have read the Contributing Guidelines
• I have tested my changes locally with mintlify dev
• All links are working correctly
• Images are properly displayed and optimized
• Code examples are tested and working
• I have updated the navigation in docs.json (if applicable)
• My changes follow the project's style guide
• I have performed a self-review of my changes
• I have added appropriate frontmatter to new pages

🧪 Testing

• Verified locally at http://localhost:3000
• Checked responsive design on mobile viewport
• Tested all code examples
• Validated all external links

📸 Screenshots (if applicable)

🔗 Related Issues

Closes #98

📝 Additional Notes

👥 Reviewers

@sancho1952007 @aagarwal1012

@dodopayments/documentation-team

Summary by CodeRabbit

• Documentation
  • Added a Regional Availability section outlining where external payment flows apply and which jurisdictions are affected.
  • Clarified “What We Handle” to read: “Global payments as per policies and local payment methods.”
  • Expanded “What You Get” to include “Compliance with regional regulations.”
  • Improved overall clarity about regional compliance and payment processing expectations to help users understand availability and constraints across markets.

[coderabbitai]

Walkthrough

Documentation updated for the iOS digital goods page to add a Regional Availability section describing where external payment flows apply, reword a “What We Handle” bullet to reference policy-compliant global payments, and add “Compliance with regional regulations” to the “What You Get” list. All edits are in features/appstore-digital-goods.mdx.

Changes

Cohort / File(s)	Summary
Docs: iOS digital goods policy clarifications features/appstore-digital-goods.mdx	Added a "Regional Availability" section detailing external payment flows and jurisdictional applicability; reworded “What We Handle” to “Global payments as per policies and local payment methods”; added “Compliance with regional regulations” under “What You Get.”

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Hop-hop, I updated the page,
Marking where payments may engage.
Policies checked, regions clear,
Compliance carrots close and near.
A gentle rabbit, notes in tow—🥕

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title, though slightly awkward in phrasing, accurately reflects the core update by indicating that the documentation now lists specific regions instead of implying global support, directly tying to the Regional Availability section added in the changeset.
Linked Issues Check	✅ Passed	The updates directly satisfy issue #98’s objectives by replacing sweeping “global” payment claims with a detailed Regional Availability section, rewording global payment statements to reflect Apple’s policy constraints, and adding compliance notes, thereby ensuring developers understand where Dodo Payments can legally replace Apple IAP.
Out of Scope Changes Check	✅ Passed	All modifications are limited to the features/appstore-digital-goods documentation file, focusing exclusively on text updates to clarify regional availability and compliance without introducing any unrelated changes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	The pull request description adheres to the repository’s template by providing a clear description of changes, marking the correct type of change, specifying the affected documentation area, completing the checklist and testing sections, including a screenshot, linking the related issue, and listing reviewers, with all required headings present.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a83d02c and 9e6e42f.

📒 Files selected for processing (1)

• features/appstore-digital-goods.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/mintlify.mdc)

Every documentation page must begin with YAML frontmatter containing title and description

Files:

• features/appstore-digital-goods.mdx

**/*.mdx

📄 CodeRabbit inference engine (.cursor/rules/mintlify.mdc)

**/*.mdx: Use clear, direct language appropriate for technical audiences
Write instructions in second person (you)
Use active voice over passive voice
Use present tense for current states and future tense for outcomes
Maintain consistent terminology across documentation
Keep sentences concise while preserving necessary context
Use parallel structure in lists, headings, and procedures
Lead sections with the most important information (inverted pyramid)
Use progressive disclosure: introduce basics before advanced topics
Break complex procedures into numbered steps using /
Include prerequisites and context before instructions
Provide expected outcomes for each major step
End sections with next steps or related information
Use descriptive, keyword-rich headings for navigation and SEO
Focus on user goals and outcomes rather than system features
Anticipate common questions and address them proactively
Include troubleshooting for likely failure points
Provide multiple pathways (beginner vs advanced) when appropriate, with an opinionated recommended path
Use for supplementary information that supports main content
Use for expert advice, shortcuts, or best practices
Use for critical cautions, breaking changes, or destructive actions
Use for neutral background or contextual information
Use for success confirmations or achievement indicators
Use to present the same concept in multiple languages
Provide complete, runnable code examples with language specified and filename when relevant
Include RequestExample/ResponseExample blocks for API endpoint docs
Document API parameters using (path, query, header, body) with types and required/defaults
Document API responses using with names, types, and required flags
Use for nested object properties or hierarchical information
Use / for platform-specific or alternative approaches
Use / for suppl...

Files:

• features/appstore-digital-goods.mdx

[offsideDebugger]

fixed it.

[whitesideofthesun]

@aagarwal1012 this can be merged. Please check the changes once.