Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions mintlify/snippets/country-support.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,6 @@ Grid is rapidly expanding. These corridors are next on our roadmap — get in to
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 China listed in both Live and Coming Soon tables

🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107

Comment:
**China listed in both Live and Coming Soon tables**

`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

How can I resolve this? If you propose a fix, please make it concise.

| 🇭🇰 Hong Kong | HK |
| 🇰🇷 South Korea | KR |
Loading