Update Google-style docstrings

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Polishes docstrings and comments across the CLIP codebase for clearer, more consistent documentation, with no functional changes. ✨

📊 Key Changes

• Standardizes docstrings to concise one-line summaries (PEP 257 style) in:
  • clip.load, _node_get, and tokenize
  • ModifiedResNet class description
  • Tokenizer helpers: bytes_to_unicode() and get_pairs()
• Minor punctuation and line-wrapping fixes for readability
• No logic, API, or behavior changes

🎯 Purpose & Impact

• Improves readability and consistency for developers and users 📚
• Enhances compatibility with documentation generators and tooling 🛠️
• Zero impact on model performance, training/inference, or user workflows ✅
• Safe update: no retraining, configuration, or code changes required from users 🚀

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/CLIP 🚀 PR! This is an automated review assistant; an Ultralytics engineer will follow up shortly. 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/CLIP 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]

🎉 Merge celebration! Huge thanks, @glenn-jocher, for refining our docs in Polish docstrings and comments across the codebase.

“Details make perfection, and perfection is not a detail.” —Leonardo da Vinci. Your thoughtful polish to docstrings and comments elevates clarity, strengthens tooling compatibility, and makes CLIP more welcoming for contributors—without touching behavior. This is the kind of craftsmanship that compounds over time.

Appreciate the care and consistency you brought here—community members will feel the difference. 🚀