[glenn-jocher]

Small copy fixes found reviewing the live compare pages after #373:

• YOLOv5 vs YOLO26: rephrase the intro ("Comparing X with Y spans that progression" → "X and Y bookend that progression")
• YOLOv5 vs EfficientDet: reword the CPU ONNX sentence so it reads naturally
• YOLOX vs YOLOv5: lowercase task names in running text

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated wording and capitalization on three model-comparison pages to make the prose clearer and task names consistent.

📊 Key Changes

• Rephrased the YOLOv5 and YOLO26 introduction to describe them as bookends of the model progression.
• Clarified that the comparison table lists CPU ONNX speeds for EfficientDet-d0 but not YOLOv5.
• Lowercased task names in running text on the YOLOX and YOLOv5 page.

🎯 Purpose & Impact

• Readers get clearer wording about the model comparisons and more consistent task-name capitalization; no technical behavior changed.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. To ensure a seamless integration of your work, 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/docs 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; the CLA check will comment with signing instructions if needed.
• ✅ 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}

Reviewed the wording changes across all three comparison pages. They are clear and consistent with the surrounding content; no issues found. LGTM.

[UltralyticsAssistant]

🎉 Thanks, @glenn-jocher, for merging this PR! The clearer model-comparison wording and consistent task-name capitalization make these pages easier to follow.

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” — Antoine de Saint-Exupéry