Update README.md

[YuhanCatherineDong]

fix: improved HTML tag formatting in README.md

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc):
• pkg.go.dev:
• goreportcard.com:
• coverage service link (codecov, coveralls, etc.):

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.
• I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Minor formatting adjustment to documentation.

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo link: missing
• pkg.go.dev: missing
• goreportcard: missing
• coverage: missing

These checks are a best-effort automation and do not replace human review.

[coderabbitai]

Walkthrough

A minor formatting adjustment to README.md adds a trailing space inside an anchor tag, resulting in a cosmetic whitespace change. No functional or logic modifications are present.

Changes

Cohort / File(s)	Change Summary
Documentation formatting README.md	Added trailing space inside anchor tag for minor formatting adjustment

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• avelino

Poem

A space so small, a trailing friend,
In README's anchor, doesn't bend—
Just whitespace dancing, neat and bright,
The README hops left and right! 🐰✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The pull request title "Update README.md" is vague and generic, using non-descriptive terminology that fails to convey what specific change was made. While the title does refer to the file being modified (README.md), it provides no indication that the change involves HTML tag formatting or a trailing space fix. A teammate scanning the repository history would not understand the primary nature or purpose of this update from the title alone, making it difficult to assess the change's significance or intent.	The title should be more descriptive and specific about the actual change. Consider revising it to something like "Fix HTML tag formatting in README.md" or "Add trailing space in anchor tag" to clearly communicate that this is a formatting fix, not a general content update. This would help maintainers and reviewers quickly understand the nature and scope of the modification.

✅ Passed checks (2 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.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d69a583 and b118e43.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Remove redundant space before </a>.

The added trailing space creates an empty text node inside the anchor, which can render as an unexpected gap next to the logo. Please drop the space so the markup closes immediately after the <img> tag.

🤖 Prompt for AI Agents

In README.md around line 3, the anchor tag contains a redundant space before the
closing </a> which creates an empty text node and may render a gap; remove the
trailing space so the </a> immediately follows the <img> tag (i.e., eliminate
the space character between the image tag and the closing anchor) to prevent the
empty text node.