fix: typo

[janoma]

Pardon my OCD.

Summary by CodeRabbit

• Documentation
  • Corrected a typographical error in the docs, updating "edge runtine" to "edge runtime" for improved clarity.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d7bbdcf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-uploadthing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 23, 2025 0:17am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
legacy-docs-uploadthing	⬜️ Ignored (Inspect)	Visit Preview		Feb 23, 2025 0:17am

[coderabbitai]

Walkthrough

The update corrects a typographical error in the documentation by replacing "edge runtine" with "edge runtime" in the FAQ page. This change solely addresses the spelling mistake in the text describing limitations for using edge functions during development in Next.js.

Changes

File(s)	Change Summary
docs/src/app/(docs)/faq/page.mdx	Corrected spelling from "edge runtine" to "edge runtime" in the documentation text.

Suggested labels

📚 documentation

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/src/app/(docs)/faq/page.mdx (1)

41-44: Typo Correction Approved

The text now correctly reads "edge runtime" instead of "edge runtine," which improves clarity and accuracy in the documentation. As a minor nitpick, consider rephrasing for enhanced flow. For example, changing the sentence to:

"If you are seeing this issue in development and are using the edge runtime, note that Next.js does not allow an edge function to fetch itself..."

might further improve readability.

🧰 Tools

🪛 LanguageTool

[style] ~41-~41: Consider an alternative verb to strengthen your wording.
Context: ...onUploadComplete calls."" If you are seeing this issue in development, and are usin...

(IF_YOU_HAVE_THIS_PROBLEM)

---

[uncategorized] ~42-~42: ‘In’ is unnecessary in most cases before the expression ‘next .’.
Context: ...ing edge runtime, there is a limitation in Next.js where it does not allow an edge func...

(CONFUSION_OF_NN_IN_NEXT_NNP)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02a800c and d7bbdcf.

📒 Files selected for processing (1)

• docs/src/app/(docs)/faq/page.mdx (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/src/app/(docs)/faq/page.mdx

[style] ~41-~41: Consider an alternative verb to strengthen your wording.
Context: ...onUploadComplete calls."" If you are seeing this issue in development, and are usin...

(IF_YOU_HAVE_THIS_PROBLEM)