From 241635701b07e00a8d92b160cceb531aace08089 Mon Sep 17 00:00:00 2001 From: Girish Patil Date: Wed, 14 Dec 2022 20:12:45 +0530 Subject: [PATCH] docs: fix wording (#44020) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) --- docs/api-reference/next/legacy/image.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-reference/next/legacy/image.md b/docs/api-reference/next/legacy/image.md index fb1acff657cf..a2c206fb36a0 100644 --- a/docs/api-reference/next/legacy/image.md +++ b/docs/api-reference/next/legacy/image.md @@ -20,7 +20,7 @@ description: Backwards compatible Image Optimization with the Legacy Image compo -Starting with Next.js 13, the `next/image` component was rewritten to improves both the performance and developer experience. In order to provide a backwards compatible upgrade solution, the old `next/image` was renamed to `next/legacy/image`. +Starting with Next.js 13, the `next/image` component was rewritten to improve both the performance and developer experience. In order to provide a backwards compatible upgrade solution, the old `next/image` was renamed to `next/legacy/image`. ## Comparison