Minor wording improvement for clarity

[Nandni-git]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Performance improvement
• Code refactoring
• Tests

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Node version:
• Browser (if applicable):
• Operating System:

Screenshots (if applicable)

Add screenshots to help explain your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have added screenshots if ui has been changed
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Additional context

Add any other context about the pull request here.

Summary by CodeRabbit

• Documentation
  • Clarified messaging regarding feature availability in the project overview.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	a315ca6

[vercel]

@Nandni-git is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update in README.md softening the language describing feature paywalling. Changed "Every basic feature" to "Most basic CapCut features" in the Why section without altering other content or structure.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Revised wording in the Why section from "Every basic feature of CapCut is paywalled now" to "Most basic CapCut features are now paywalled," moderating the assertion about feature availability.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A word here, a word there,
From "every" to "most" with care,
The truth now sits less severe,
Documentation bright and clear! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description uses the repository template but lacks specific details about the actual changes made and their motivation.	Add a clear summary of the wording changes made (e.g., what was changed and why), fill in the issue number if applicable, provide test details, and complete the checklist items appropriately.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Minor wording improvement for clarity' accurately describes the main change—updating README.md wording from 'Every' to 'Most' for clarity.
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 docstrings

---

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