Repository navigation
Conversation
- examples/with-a2a-server: "message/taks endpoints" -> "message/task endpoints" - README and i18n READMEs (jp, kr): image alt text "dashboar" -> "dashboard" - whatsapp-order recipe and example: "platfrom" -> "platform" - blog: "Accesible" -> "Accessible", "programatically" -> "programmatically"
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The documentation corrections introduce no identified behavior or operational risk, so the PR appears ready to merge after normal checks. Pre-merge checks ·
|
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
A handful of typos in the READMEs, an example, two recipe pages and two blog posts:
examples/with-a2a-server/README.mdsays theA2AServerexposes "message/taks endpoints".README.md,i18n/README-jp.mdandi18n/README-kr.mdhavealt="dashboar"on the VoltOps screenshot. The two Chinese READMEs already usealt="dashboard".website/recipes/whatsapp-order.mdandwebsite/examples/whatsapp-order.mdlink to the "VoltOps LLM Observability platfrom".website/blog/2025-05-01-voltagent-marketplace/index.mdhas "Accesible Solutions".website/blog/2025-07-20-llm-evaluation/index.mdhas "programatically".What is the new behavior?
Each of the above is corrected: "message/task endpoints",
alt="dashboard", "platform", "Accessible", "programmatically".Notes for reviewers
Markdown only, one line per file. No changeset added since no package is affected.
Summary by cubic
Fixes typos across READMEs, examples, recipes, and blog posts without affecting any code.
README.md,i18n/README-jp.md, andi18n/README-kr.md.Written for commit b5a07c9. Summary will update on new commits.
Summary by CodeRabbit