Update onboarding region screenshot: AP region is Taiwan, not Hong Kong

[mykolaxboiko]

Summary

Replaces docs/platform/platform-onboarding-region-map-with-latency.avif in place (same filename — published paths are a stable public API).

The previous screenshot predated ultralytics/portal PR #1781 (April 2026) and still showed the Asia Pacific region as Hong Kong, contradicting the region table right below it on https://docs.ultralytics.com/platform/quickstart/#region-selection and the actual infrastructure (asia-east1, Taiwan — moved from Hong Kong in portal PR #576, Jan 2026). Reported by Abi in Slack.

New capture from the current onboarding flow shows Asia Pacific — Taiwan.

• Format: AVIF, 1280×832 (standard docs screenshot dimensions)
• Size: 18.3 KB (previous: 27.4 KB)
• Deleted: the stale Hong Kong screenshot content (binary replaced in place; no path or docs markdown changes needed)

After merge, purge the jsDelivr cache so the fix is visible immediately:

curl https://purge.jsdelivr.net/gh/ultralytics/assets@main/docs/platform/platform-onboarding-region-map-with-latency.avif

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updates the onboarding region map screenshot to correctly show the AP region as Taiwan instead of Hong Kong. 🗺️

📊 Key Changes

• Replaces docs/platform/platform-onboarding-region-map-with-latency.avif with an updated onboarding region screenshot.
• Corrects the AP region labeling/visual reference from Hong Kong to Taiwan.

🎯 Purpose & Impact

• Improves documentation accuracy for Ultralytics Platform onboarding. ✅
• Reduces potential confusion for users selecting or reviewing AP region availability. 🌏

📋 Skipped 1 file (lock files, generated, images, etc.)

• docs/platform/platform-onboarding-region-map-with-latency.avif

Old image:

New image:

[github-actions]

👋 Hello @mykolaxboiko, thank you for submitting a ultralytics/assets 🚀 PR! This automated message confirms we’ve received your contribution, and an Ultralytics engineer will assist with review. To ensure a seamless integration of your screenshot update, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/assets main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀