-
Notifications
You must be signed in to change notification settings - Fork 365
docs: Clarify image optimization setup in Next.js, fix some typos #1196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
WalkthroughMinor wording corrections were made in two documentation files to improve grammatical clarity. Redundant words were removed from sentences describing image optimization setup in Next.js and the Changes
Suggested labels
Suggested reviewers
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@max-17 is attempting to deploy a commit to the Ping Labs Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/src/app/(docs)/working-with-files/page.mdx (1)
35-35
: Great clarification—extra “allow” removed
The revised sentence “to setup image optimization in Next.js that only allows” is much clearer without the redundant “allow.”Nit-pick: since this is a verb use, consider changing “setup” to “set up” (two words) for grammatical accuracy.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~35-~35: ‘In’ is unnecessary in most cases before the expression ‘next .’.
Context: ...mple of how to setup image optimization in Next.js that only allows optimizing images f...(CONFUSION_OF_NN_IN_NEXT_NNP)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/src/app/(docs)/working-with-files/page.mdx
(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/src/app/(docs)/working-with-files/page.mdx
[uncategorized] ~35-~35: ‘In’ is unnecessary in most cases before the expression ‘next .’.
Context: ...mple of how to setup image optimization in Next.js that only allows optimizing images f...
(CONFUSION_OF_NN_IN_NEXT_NNP)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/src/app/(docs)/api-reference/ut-api/page.mdx (2)
174-174
: Typo fix: removed redundant “is”
The extra “is” in the default value description has been correctly removed, improving readability.Consider using “Defaults to […]” instead of “Default value is […]” for consistency with other property docs.
262-262
: Typo fix: removed redundant “is”
The duplicate “is” in theopts.acl
description has been removed as intended.You may also unify phrasing to “Defaults to […]” here to match the style used elsewhere.
I read that sentence at least 10 times. Did not understand the meaning until I saw the code below. For context: English is not my first language
Summary by CodeRabbit