editted and checked readme file

[iabhinavsahu]

Readme file named Future instead of feature , which I changed and pushed back

Summary by CodeRabbit

• Documentation
  • Corrected terminology: renamed "Futures" to "Features" across the README.
  • Updated section header and summary text to reflect "Features".
  • Adjusted three list items wording/casing from "Refer future", "Redeem Code Future", "Top Trending future" to "Refer feature", "Redeem Code Feature", "Top Trending feature".

[coderabbitai]

Walkthrough

README.md updated to correct terminology: the "Futures" section header and its three bullet items were changed to "Features" and corresponding wording ("future" → "feature") only; no code or API changes.

Changes

Cohort / File(s)	Summary
Documentation terminology update README.md	Section header changed from "Check Bot Futures" to "Check Bot Features"; three bullet items renamed to replace "future" with "feature" ("Refer feature", "Redeem Code Feature", "Top Trending feature")

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Purely documentation text replacements; no logic or API changes.

Poem

🐰 I hopped through words to make them clear,
Futures trimmed, now features near,
A tiny fix, a tidy cheer,
Docs refreshed — the rabbit's here! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The title "editted and checked readme file" uses vague, non-descriptive language that fails to convey what specifically was changed in the README. While the title does reference the README file that was modified (a real part of the changeset), the phrases "editted and checked" don't specify the actual nature of the change. The PR description reveals the main change was correcting terminology from "Future" to "Feature" throughout the file, but this substance is completely absent from the title. Additionally, the title contains a spelling error ("editted" should be "edited"). Without reading the description, a teammate scanning PR history would not understand the specific purpose of this change.	Consider revising the title to be more descriptive and specific, such as "Fix terminology: change 'Future' to 'Feature' in README" or "Correct 'Futures' to 'Features' throughout README". This would clearly communicate the substantive change while also correcting the spelling error. A more descriptive title helps teammates understand the PR's purpose at a glance.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18b8ba8 and 245f697.

📒 Files selected for processing (1)

• README.md (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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 549ce66 and 18b8ba8.

📒 Files selected for processing (1)

• README.md (2 hunks)

🔇 Additional comments (1)

README.md (1)

55-57: Content terminology corrections look good.

The three bullet items have been correctly updated from "future" to "feature" terminology, improving clarity and consistency with standard documentation practices.