Fix hyphenation in README

[23f2005050]

Hi maintainers 👋

I noticed a minor hyphenation issue in the README and fixed it.

Change:

• Updated "Express inspired" → "Express-inspired"

Thank you for your work on Fiber 🙂

Description

Please provide a clear and concise description of the changes you've made and the problem they address. Include the purpose of the change, any relevant issues it solves, and the benefits it brings to the project. If this change introduces new features or adjustments, highlight them here.

Fixes # (issue)

Changes introduced

List the new features or adjustments introduced in this pull request. Provide details on benchmarks, documentation updates, changelog entries, and if applicable, the migration guide.

• Benchmarks: Describe any performance benchmarks and improvements related to the changes.
• Documentation Update: Detail the updates made to the documentation and links to the changed files.
• Changelog/What's New: Include a summary of the additions for the upcoming release notes.
• Migration Guide: If necessary, provide a guide or steps for users to migrate their existing code to accommodate these changes.
• API Alignment with Express: Explain how the changes align with the Express API.
• API Longevity: Discuss the steps taken to ensure that the new or updated APIs are consistent and not prone to breaking changes.
• Examples: Provide examples demonstrating the new features or changes in action.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• Enhancement (improvement to existing features and functionality)
• Documentation update (changes to documentation)
• Performance improvement (non-breaking change which improves efficiency)
• Code consistency (non-breaking change which improves code reliability and robustness)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

• Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
• Conducted a self-review of the code and provided comments for complex or critical parts.
• Updated the documentation in the /docs/ directory for Fiber's documentation.
• Added or updated unit tests to validate the effectiveness of the changes or new features.
• Ensured that new and existing unit tests pass locally with the changes.
• Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
• Aimed for optimal performance with minimal allocations in the new code.
• Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

[gemini-code-assist]

Summary of Changes

Hello @23f2005050, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a small but important grammatical correction within the project's README file. The change specifically targets a hyphenation inconsistency, ensuring that the phrase describing Fiber's inspiration is correctly formatted. This refinement enhances the overall professionalism and clarity of the project's introductory documentation.

Highlights

• Documentation Fix: Corrected a minor hyphenation issue in the README, changing "Express inspired" to "Express-inspired" for improved grammatical accuracy and readability.

Changelog

• .github/README.md
  • Fixed hyphenation of "Express inspired" to "Express-inspired".

Activity

• The author, 23f2005050, identified and corrected a minor hyphenation issue in the README.
• The author expressed gratitude for the work on Fiber.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Walkthrough

This pull request updates the README documentation, changing the phrasing "Fiber is inspired by Express" to "Fiber is Express-inspired" in the Philosophy section to improve clarity.

Changes

Cohort / File(s)	Summary
Documentation Rewrite .github/README.md	Updated phrasing of Fiber's relationship to Express from "inspired by" to "Express-inspired" in Philosophy section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• 📚 Doc: Update intro documentation #3204: Makes the same documentation wording change—converting the description to "Express-inspired"—across related documentation files.

Suggested labels

📒 Documentation

Suggested reviewers

• gaby
• sixcolors
• efectn

Poem

🐰 A rabbit hops through words with care,
Express-inspired, beyond compare!
"Inspired by" becomes so sleek,
Just two words make the prose unique.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: a minor hyphenation fix in the README where 'Express inspired' was changed to 'Express-inspired'.
Description check	✅ Passed	The author provided a brief, clear explanation of the change at the top but left most template sections incomplete with unchecked checkboxes, which is appropriate for a minor documentation fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[gemini-code-assist]

Code Review

This pull request aims to fix a perceived hyphenation issue in the README.md file by changing 'inspired by Express' to 'Express-inspired'. However, the original phrasing was grammatically correct and arguably clearer. The proposed change introduces a slightly awkward sentence structure and removes intentional emphasis. My review includes a comment suggesting to revert this change to restore the original, more readable text.

[gemini-code-assist]

Thank you for your contribution. The original phrasing **inspired** by Express was grammatically correct and clear. The new phrasing 'Fiber is Express-inspired...' is less standard, as compound adjectives like 'Express-inspired' are typically used before a noun (e.g., 'an Express-inspired framework'). The original phrasing is more common and readable in this context. Furthermore, this change removes the bold formatting, which was likely intended for emphasis. For these reasons, reverting to the original text is recommended.

Suggested change

	Fiber is Express-inspired, the most popular web framework on the Internet. We combined the **ease** of Express and **raw performance** of Go. If you have ever implemented a web application in Node.js (_using Express or similar_), then many methods and principles will seem **very common** to you.
	Fiber is **inspired** by Express, the most popular web framework on the Internet. We combined the **ease** of Express and **raw performance** of Go. If you have ever implemented a web application in Node.js (_using Express or similar_), then many methods and principles will seem **very common** to you.

[gaby]

@23f2005050 The change is grammatically incorrect. The correct way in English is Fiber is **inspired** by Express