From c0bf9ef5a503848110dcb723ffc21ceaf4ed8bf4 Mon Sep 17 00:00:00 2001 From: JamBalaya56562 Date: Fri, 6 Dec 2024 17:20:22 +0900 Subject: [PATCH] docs: fix code block language in images-and-fonts docs --- docs/01-app/01-getting-started/04-images-and-fonts.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/01-app/01-getting-started/04-images-and-fonts.mdx b/docs/01-app/01-getting-started/04-images-and-fonts.mdx index 80d04454ffad0..fb2f5ec233779 100644 --- a/docs/01-app/01-getting-started/04-images-and-fonts.mdx +++ b/docs/01-app/01-getting-started/04-images-and-fonts.mdx @@ -55,7 +55,7 @@ The `src` property can be a [local](#local-images) or [remote](#remote-images) i To use a local image, `import` your `.jpg`, `.png`, or `.webp` image files from your [`public` folder](#handling-static-assets). -```tsx filename="app/page.ts" switcher +```tsx filename="app/page.tsx" switcher import Image from 'next/image' import profilePic from './me.png' @@ -131,7 +131,7 @@ Since Next.js does not have access to remote files during the build process, you Then, to safely allow images from remote servers, you need to define a list of supported URL patterns in `next.config.js`. Be as specific as possible to prevent malicious usage. For example, the following configuration will only allow images from a specific AWS S3 bucket: -```ts filename="next.config.js" switcher +```ts filename="next.config.ts" switcher import { NextConfig } from 'next' const config: NextConfig = {