docs: visual spacing glitch between badges.

[canmi21]

Before:

After:

Summary by CodeRabbit

• Documentation
  • Simplified README presentation by consolidating badges and partner banners into two centered paragraph blocks.
  • Replaced multiple centered divs with cleaner inline markup for improved readability and easier maintenance.
  • Preserves existing content, links, and semantics; no changes to navigation or behavior.
  • Visual layout remains consistent for readers.
  • No code or API changes involved.

[coderabbitai]

Walkthrough

Reformats README.md by replacing multiple centered divs for badges and partner banners with two centered paragraph blocks. Content is unchanged; only presentation markup is consolidated and simplified.

Changes

Cohort / File(s)	Summary
Docs: README formatting README.md	Replaced multiple centered div containers with two centered paragraph blocks for badges and partner banners; consolidated repeated markup into inline elements without changing content or links.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: Fix README images #5162 — Also restructures README badge/partner presentation markup, indicating a similar documentation layout change.

Poem

Hoppity hop, I tidy with glee,
Badges in rows, neat as can be.
No logic to nudge, no code to rearrange—
Just paragraphs dancing in a gentle change.
Carrot-approved README, crisp and clean! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title check	✅ Passed	The title 'docs: visual spacing glitch between badges.' directly aligns with the PR's primary objective of fixing visual spacing issues between README badges.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[canmi21]

Hi @tannerlinsley It seems that this PR has been going on for a long time. Could you please Reiew? Thank you