Fix typo in valid request description

[TheUntraceable]

Corrected a typo in the description of valid requests.

What does this PR do?

Fix a major typo.

Fixes # (issue)
I tried to click the link to the contributing but it 404'd. https://engineering.unkey.com/contributing. I don't think that's needed for this typo fix lol

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Blog post
• Changelog
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How should this be tested?

By activating neurons within the brain and deeply thinking and researching to recognise the spelling for providing is correct now.

Checklist

• Filled out the "How to test" section in this PR
• Read Contributing Guide
  • there is none
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR

Summary by CodeRabbit

• Bug Fixes
  • Corrected a spelling error on the Pricing page ("providing").
• Documentation
  • Updated contributing guide link in the README to the new documentation URL.

[vercel]

@TheUntraceable is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

Fixed two minor text edits: corrected "proividng" to "providing" on the Pricing page and updated the contributing guide URL in README.md from https://engineering.unkey.com/contributing to https://engineering.unkey.com/docs/contributing. No functional or exported-API changes.

Changes

Cohort / File(s)	Summary
Content typo apps/www/app/pricing/page.tsx	Fixed misspelling: "proividng" → "providing" in the "What counts as valid?" paragraph.
Docs link update README.md	Updated contributing guide URL from https://engineering.unkey.com/contributing to https://engineering.unkey.com/docs/contributing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit read the README late at night,
Spotted a typo and a link not quite right.
With nibble and nudge and a hop of delight,
I fixed the words and set URLs bright. 🐇✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ 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%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	The description covers most required sections but lacks clarity on the actual issue number and has informal test instructions.	Add the specific issue number in 'Fixes #' field and provide more concrete, professional test instructions instead of the humorous phrasing.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the primary change: fixing a typo in the valid request description.

_{✏️ 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

---

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

[TheUntraceable]

I hope you appreciate my humour

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

README.md (1)

1-17: ⚠️ Potential issue | 🟡 Minor

Add the required bug-fix tracker Markdown file

This PR modifies Markdown but does not include the required bug-fix tracker .md documenting tasks/progress and a Root Cause Hypotheses section. Please add it to satisfy repo standards.

As per coding guidelines, " *.md: Create a bug-fix tracker .md file to keep track of tasks and progress for each bug fix" and "When analyzing code to formulate hypotheses about the root cause, add them in a 'Root Cause Hypotheses' section in your bug-fix tracker .md file".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 1 - 17, Add the required bug-fix tracker Markdown
file documenting tasks/progress and a "Root Cause Hypotheses" section: create a
new .md tracker (e.g., bugfix-<short-descr>.md) alongside the changed docs,
include a concise Title, a Task checklist with owner/status/progress entries,
and a clearly labeled "Root Cause Hypotheses" heading listing any analyzed
causes and supporting notes; ensure the tracker is committed with the PR so the
repository's *.md guideline is satisfied.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@README.md`:
- Around line 1-17: Add the required bug-fix tracker Markdown file documenting
tasks/progress and a "Root Cause Hypotheses" section: create a new .md tracker
(e.g., bugfix-<short-descr>.md) alongside the changed docs, include a concise
Title, a Task checklist with owner/status/progress entries, and a clearly
labeled "Root Cause Hypotheses" heading listing any analyzed causes and
supporting notes; ensure the tracker is committed with the PR so the
repository's *.md guideline is satisfied.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d49da21 and 3912dee.

📒 Files selected for processing (1)

• README.md