Fix redirected URLs

[glenn-jocher]

Summary

• update redirected external URLs to their final destinations
• apply the redirect cleanup across tracked documentation and related text files

Testing

• no tests run (link-only changes)

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR makes small but important README fixes in both English and Chinese, updating outdated license and YouTube links for better accuracy and reliability 🔗✨

📊 Key Changes

• Updated the AGPL-3.0 license link in README.md from an older Open Source Initiative URL to the correct current one ✅
• Applied the same license link fix in README.zh-CN.md to keep the Chinese documentation aligned 🌍
• Changed the YouTube channel URL in both README files from youtube.com to www.youtube.com for a more consistent and explicit link format 📺
• Kept changes limited to documentation only, with no app code or functionality changes 🛠️

🎯 Purpose & Impact

• Improves documentation accuracy, so users are directed to the correct AGPL-3.0 license page 📘
• Reduces the chance of broken, outdated, or ambiguous links when readers check licensing or social channels 🔍
• Keeps the English and Chinese READMEs consistent, which helps international users and maintainers 🤝
• Has no effect on app behavior, but improves trust and polish in the project’s public-facing docs 💡

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/yolo-flutter-app 🚀 PR! This is an automated message to help streamline review, and an engineer will assist you shortly. Please review the checklist below for smooth integration 😊

• ✅ 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/yolo-flutter-app 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! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Clean documentation-only change. The updated OSI and YouTube URLs are consistent across both README files, match the PR intent, and do not introduce any obvious issues in the changed lines.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[UltralyticsAssistant]

🎉 Merged — thank you, @glenn-jocher!

These README updates may be small on the surface, but they make a meaningful difference for clarity, consistency, and trust across the project. Keeping both the English and Chinese docs aligned with accurate license and YouTube links helps ensure a smoother experience for everyone who discovers and uses the app.

As Leonardo da Vinci said, “Details make perfection, and perfection is not a detail.” This PR is a great example of that spirit — thoughtful documentation polish that strengthens the project without changing a line of app functionality.

Really appreciate your care and attention here 🙌