chore: fix typo in example apps documentation

[saikumarrs]

PR Description

I've fixed a typo on the Vercel serverless application example's documentation.

Linear task (optional)

N/A

Cross Browser Tests

Please confirm you have tested for the following browsers:

• Chrome
• Firefox
• IE11

Sanity Suite

• All sanity suite test cases pass locally

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Summary by CodeRabbit

• Documentation
  • Corrected a typographical error in the URL provided in our deployment guidance, ensuring the documentation is accurate and user-friendly.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request corrects a typographical error in the documentation. The URL for the Vercel Edge example in the USAGE.md file was updated to fix the misspelling from "vencel-edge" to "vercel-edge". The change affects only the documentation and does not impact any functionality or underlying logic.

Changes

File Path	Change Summary
examples/serverless/USAGE.md	Updated the documentation link by correcting the URL from "vencel-edge" to "vercel-edge".

---

📜 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 7952ad3 and 21fbc13.

📒 Files selected for processing (1)

• examples/serverless/USAGE.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• examples/serverless/USAGE.md

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Security and code quality checks
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Bundle size checks
• GitHub Check: Unit Tests and Lint

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.36%. Comparing base (7952ad3) to head (21fbc13).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2036   +/-   ##
========================================
  Coverage    61.36%   61.36%           
========================================
  Files          478      478           
  Lines        16394    16394           
  Branches      3249     3245    -4     
========================================
  Hits         10060    10060           
- Misses        5082     5127   +45     
+ Partials      1252     1207   -45     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[saikumarrs]

It addresses the issue,
#2004.